Skip to main content
Tools are actions your AI assistant can perform on your behalf. They’re organized into read tools (fetching data) and write tools (making changes).
Write tools that involve money — like initiating payments — always require your confirmation in the Moneda app before anything happens.

Response shape

Every tool response is TOON-encoded (~40% fewer tokens than equivalent JSON) and runs through a safety-net scrubber that drops null, undefined, "", empty arrays, and empty objects from the payload before serialisation. 0, false, and "0" are preserved — a balance of zero is a real answer. What this means in practice:
  • If a field is a known optional that has no value for your account (e.g. imageUrl on recovery contacts, bankName on an ACH-only bank entry), it’s simply absent from the response rather than serialised as "null".
  • If a list tool finds no matching rows, the array field itself is absent and the count field (always present) is the authoritative “nothing matched” signal. Example: { "count": 0 } instead of { "results": [], "count": 0 }.
  • Robust MCP clients handle absent fields transparently. Prompt-engineered clients that assert exact key presence may need a small update — check for the count field first.

What read tools are available?

View details →

What write tools are available?

View details →

Learn more

Resources

Data your AI reads automatically for context.

Scopes

Permission scopes that control tool access.

Use cases

See what you can do with these tools in practice.

Quickstart

Get connected in 5 minutes.