What is not a tool

Fifteen 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 58 tools, nearly all of them tools the Miles chat pipeline calls too. The chat pipeline's other tools 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.
`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.
`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.
`get_account_preferences`	Standing constraints a member sets in chat, such as a pause on new applications. They are a new kind of member data, and the consent screen does not name it yet, so no connected app can read them.
`set_account_preference`	Writes that same data, so it waits with the read.
`remove_account_preference`	Removes one of those constraints, so it waits with the read.
`derive_valuations_interview`	Works out what a point is worth to a member from how they redeem. No model call and no network, so nothing disqualifies it: it is held back on cost alone. Its seven parameters put the advertised tool list over the size ceiling every MCP turn pays for, and that is a decision of its own.
`confirm_valuation_change`	Saves a valuation change that chat proposed in an earlier reply. A connected app has no Miles conversation to confirm in, and `set_valuation` already writes directly once you grant write access.
`product_help`	Answers questions about the Miles website and app itself (features, FAQ). A client connected over MCP is not browsing askmiles.ai, so the same corpus has no clear use there yet.
`set_subject_profile`	Internal: records what a member says about someone else's cards for one chat turn. A connected app has no such turn, so there is nothing for it to call.
`plan_welcome_offers`	Plans where a stated amount of spend should go to earn welcome offers, from the member's own wallet and saved preferences. It ships in chat first; a connected app does not have it yet.

If you need one of these

Snapshots are generated and shared from the site. Account preferences are set in chat on askmiles.ai. Everything else has a tool that presents the same data in a supported shape; see MCP tools.