Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getmoneymovements

getMoneyMovements

Retrieves all money movements for a specified YNAB plan, enabling you to review transfers and balance changes within that budget.

Instructions

Returns all money movements

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": "getMoneyMovements"
  }
}

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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and delivers very little. It does not state that this is a read-only operation, whether the result is paginated, whether it requires an authenticated plan context, or what the movements represent; only the word "all" conveys any behavioral information.

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

Conciseness3/5

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

A single short sentence with no wasted words and nothing to trim, but it is under-specified rather than concise. The one clause that exists is front-loaded correctly, so the structure is fine; the content is thin.

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?

With no annotations and no output schema, the description should compensate by describing read-only behavior and what a money movement contains, and it does neither. For a tool whose only parameter is well documented, the remaining gap is the behavioral story, which is essentially absent.

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?

There is a single required parameter with 100% schema description coverage, including detailed explanation of the "last-used" and "default" sentinel values, so the schema does the work. The description adds no meaning beyond what the schema provides, which is the baseline case of 3.

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

Purpose3/5

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

"Returns all money movements" states a verb and a resource, so the basic operation is inferable, but there is no scope detail (date range? plan-wide?) and no differentiation from siblings such as getMoneyMovementsByMonth or getMoneyMovementGroups. The agent cannot tell from the description alone whether this is the unfiltered listing or something else.

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 gives no when-to-use guidance, no prerequisites, and does not point to any alternative tool. The word "all" hints at an unfiltered listing, which implicitly contrasts with the ByMonth variants, but that contrast is never made explicit and the agent must infer it from sibling names.

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