What is not a tool

Ten capabilities the chat pipeline has that the MCP server deliberately does not expose, and the reason for each.

Why a list exists

The MCP server exposes 47 of the tools the Miles chat pipeline can call. The rest are withheld on purpose, and the reasons are worth knowing before an agent goes looking for one. The rule behind most of them: a tool on this server never spends a Miles model call, and never lets a client write something Miles cannot read back safely.

Withheld, and why

Name	Why it is not here
`generate_snapshot`	Generates its sections with a Miles model call. Exposing it would let a client spend Miles' inference on Miles' bill.
`share_snapshot`	Shares that generated output, so it is withheld with it.
`set_balances`	Balances are stored as plain JSON, and a bad write corrupts every transfer plan downstream. Reading balances is a tool; writing them stays in chat, where Miles checks the shape first.
`calculate`	An agent does its own arithmetic. An arbitrary expression evaluator is attack surface bought for nothing.
`web_search`	A dead registry entry with no server wrapper. Web lookup is `knowledge_search`'s internal fallback, not a tool of its own.
`request_reasoning`	Internal to the chat pipeline: how one stage hands off to the next.
`finalize_analysis`	Internal: the signal that ends the pipeline's reasoning loop.
`get_user_data`	Internal: raw session and profile plumbing that `get_wallet_summary` and friends present properly.
`get_wallet`	Internal: the pipeline's own wallet loader. `get_wallet_cards` is the tool.
`get_wallet_with_card_info`	Internal, same loader with catalog joins. `get_card_info` with a wallet id does this for one card.

If you need one of these

Balances are written in chat on askmiles.ai, or through the balances ledger in the wallet. Snapshots are generated and shared from the site. Everything else has a tool that presents the same data in a supported shape; see MCP tools.