swaitsandClaude Opus 5.5
7741e96eb3
check / check (push) Canceled after 0s
The owner (2026-10-23): "We should probably just delete the stdio path altogether. THere's no point in that. And it sitting there unused will just lead to bitrot. Nuke it?" Books are served only by the books server (`wanderbooks server`), reached by agents through the bridge (`wanderbooks mcp --book ID`), which stays. Removed: `wanderbooks dev-stdio`, the `ledger-mcp` binary, and `ledger_mcp::run` (stdio and `--http` over a bare data dir), with all that only that mode had: - files the books make coming back inline: `HandedFile.content_base64` is gone, and `download` and `expires_at` are always there; - books with no access log or backups: `books.access_log`, `books.backup` and `books.back_up_now` are always offered, by scope; - the settings file read and reloaded (`legacy_files`), the vault key named by a file or `--vault-key-file`, and the books dir's key-inside-the-books and git checks (with `paths.rs`); - `wire.rs` (the bridge frames an agent's lines itself); - `books.settings`' file fields and `books.start`'s `settings_source`. `BooksServer` is built one way, from `Served` (a book as the books server serves it), in production and in the unit tests. An unknown tool is now a protocol error (mcp-tools.md). Inline file input is unchanged. Then the owner's three decisions (2026-10-23, the question tool): (a) `books.import_settings` is removed entirely (118 tools): old books come in whole by `wanderbooks books adopt`, which reads their settings file once; ledger-config keeps its settings-file parsing only as far as adoption uses it (`load` and the path-reading `effective_receipt_policy` are gone), and `books.chart_template` gives its settings as `books.set_setting` changes. (b) The viewer's loose-books-folder mode is removed (`--data-dir`, `--books-toml`, `--vault-key-file`, the settings file and config.json followed): it opens only books of the data root, reading settings from the journal and the vault from the book's own `vault/` and `keys/`. (c) `wanderbooks dev-stdio` has no stub: it is an unknown command like any other word. Also: an upload's expiry past the calendar is an error, never an empty string. Tests: every suite that drove the stdio server moved to crates/ledger-cli/tests/ and drives a real `wanderbooks server` on a data root of its own (tests/common), handed files by their download; mcp_stdio.rs is mcp_journeys.rs. Tests of what is gone are deleted and listed in docs/testing.md. Docs: plan D-44 (D-18 superseded), STATUS, testing, rules, mcp-interface, the handbook, README; justfile recipes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T3gXMVt7XJPi6ens1or9Dj
49 lines
1.6 KiB
Markdown
49 lines
1.6 KiB
Markdown
# Model Context Protocol: tools (specification 2025-06-18)
|
|
|
|
Governs `ledger-mcp`'s tool results and errors. Source:
|
|
https://github.com/modelcontextprotocol/modelcontextprotocol,
|
|
docs/specification/2025-06-18/server/tools.mdx (MIT). Fetched 2026-10-14.
|
|
|
|
**Structured Content**
|
|
|
|
> **Structured** content is returned as a JSON object in the
|
|
> `structuredContent` field of a result.
|
|
>
|
|
> For backwards compatibility, a tool that returns structured content
|
|
> SHOULD also return the serialized JSON in a TextContent block.
|
|
|
|
**Output Schema**
|
|
|
|
> Tools may also provide an output schema for validation of structured
|
|
> results. If an output schema is provided:
|
|
>
|
|
> - Servers **MUST** provide structured results that conform to this schema.
|
|
> - Clients **SHOULD** validate structured results against this schema.
|
|
|
|
**Error Handling**
|
|
|
|
> Tools use two error reporting mechanisms:
|
|
>
|
|
> 1. **Protocol Errors**: Standard JSON-RPC errors for issues like:
|
|
> - Unknown tools
|
|
> - Invalid arguments
|
|
> - Server errors
|
|
>
|
|
> 2. **Tool Execution Errors**: Reported in tool results with `isError: true`:
|
|
> - API failures
|
|
> - Invalid input data
|
|
> - Business logic errors
|
|
|
|
**Security Considerations**
|
|
|
|
> 1. Servers **MUST**:
|
|
> - Validate all tool inputs
|
|
> - Implement proper access controls
|
|
> - Rate limit tool invocations
|
|
> - Sanitize tool outputs
|
|
|
|
(A local books server for one company's agents: access control is the
|
|
bearer tokens and their scopes on the data root's private sockets, and
|
|
rate limiting has no one to limit; wanderbooks takes "validate all tool
|
|
inputs" and "sanitize tool outputs" as binding.)
|