Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getaccounts

getAccounts

Retrieve all accounts for a YNAB plan, with optional server knowledge filtering to return only changed entities.

Instructions

Returns all accounts

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "plan_id": "<plan_id>"
    },
    "name": "getAccounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesThe id of the plan. "last-used" can be used to specify the last used plan and "default" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
last_knowledge_of_serverNoThe starting server knowledge. If provided, only entities that have changed since `last_knowledge_of_server` will be included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden, but "Returns" merely implies a read operation. It does not disclose plan scoping or that last_knowledge_of_server can limit results to changed entities; the unqualified "all accounts" can therefore be misleading for incremental calls.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The operation and resource are front-loaded in a waste-free, easily parsed sentence. It is excessively terse for selection and behavioral guidance, but there is no redundancy or structural confusion.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although the complete schema makes a syntactically valid invocation possible, the description relies almost entirely on it and adds no plan-scope or single-account-versus-list context. With no annotations or output schema, and with "all" obscuring incremental behavior, the definition remains substantially under-contextualized.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3: the schema already explains plan_id, its special values, and last_knowledge_of_server. The description adds no parameter meaning beyond those structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Returns all accounts" clearly states a retrieval verb and the account resource, implying a list operation. It does not mention that retrieval is scoped by the required plan_id or distinguish the tool from getAccountById, so it falls short of top-tier clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no explicit guidance about when to use this tool versus getAccountById or when to perform incremental retrieval. The word "all" only weakly implies a full-list use case and does not explain the available delta-style request.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.