> For the complete documentation index, see [llms.txt](https://shinkalabs.gitbook.io/hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shinkalabs.gitbook.io/hub/andromeda/mcp-reference/tools.md).

# Tool catalogue

Andromeda's MCP server exposes around 70 tools, one per REST route, generated from the same route catalogue that drives the HTTP API. There is nothing to keep in sync: if a route exists, the tool exists, with the same inputs and the same behaviour. (`GET /capabilities` reports the exact count.)

## How tools map to routes

Each tool corresponds to one REST operation. A tool's name and input schema follow the operation it mirrors, so once you know the [REST surface](/hub/andromeda/api-reference/overview.md), you know the tools. Inputs are validated the same way; outputs are the same JSON.

## What is covered

* **dWallets & signing**: `create_dwallet` (passphrase-wrapped, server-side DKG; with `attachRecoveryPolicy` it also deploys a rules-policy and delegates the dWallet so it's signable + recoverable from the first call), `transfer_ownership` (delegate a bare dWallet's authority), `approve` (the owner authorises a message → returns the approval proof for `sign_message`), `presign`, `sign_message`; plus the low-level pair (DKG prepare/submit, sign/submit) for clients that run the MPC client side themselves; future-sign and complete; imported keys; re-encrypt share; make share public; list presignatures. See [Create a dWallet](/hub/andromeda/getting-started/create-dwallet.md) and [Sign a message](/hub/andromeda/getting-started/sign.md).
* **Recovery**: discovery (challenge, resolve), recovery policy (preview, deploy, admin challenge/submit, apply pending, read), primary recovery (challenge, submit), quorum sessions (open, contribute, finalize, close, read).
* **Identity**: email magic link (request, verify), and OAuth/passkey flows where the deployment enables them.
* **Policies**: for each of the eight templates, preview, deploy, read, and challenge-based admin actions (change, and `revoke`); plus the per-policy SDK metadata.
* **Webhooks**: register and manage endpoints.
* **Future-Sign**: arm triggers, manage them.
* **Audit log**: query entries and verification data.
* **Encrypt FHE**: ciphertexts, graphs (execute, register, execute-registered, commit, submit, status, operations), DSL (types, op), decrypt (request, poll), NEK, authorities, fees, ownership, events, private transactions, wallet balance.
* **Introspection**: capabilities, pricing, pricing estimate.

For the exact tool list and input schemas, connect a client (see [Connect](/hub/andromeda/mcp-reference/connect.md)) and list the tools, or read the [OpenAPI spec](https://api.andromedainfra.pro/openapi.json); the two correspond one to one.

## Scopes

A tool requires the same scope as its REST route: `read` for read-only tools, `write` for mutations, `admin` for webhooks / audit / policies / future-sign. Quota is charged per call at the REST cost.

## Idempotency

Pass an `Idempotency-Key` with a tool call to make a retry safe; the same body with the same key replays the previous result. See [Idempotency keys](/hub/andromeda/guides/idempotency.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://shinkalabs.gitbook.io/hub/andromeda/mcp-reference/tools.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.