Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getmoneymovementgroups

getMoneyMovementGroups

Retrieve all money movement groups for a specified YNAB plan to review how funds move between categories and accounts.

Instructions

Returns all money movement groups

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

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 burden of behavioral disclosure and delivers almost nothing. It does not say whether the result is scoped to a plan, whether it is paginated, whether it is read-only, or what a money movement group contains.

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?

One short, front-loaded sentence with no wasted words, but its brevity reflects under-specification rather than efficiency. There is no structure beyond the bare statement of return.

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 is the only source of behavioral context, and it omits what the tool returns, how many groups come back, and how it relates to its month-scoped siblings. It is not sufficient for confident selection.

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?

The single plan_id parameter is fully described in the schema, including the "last-used" and "default" sentinels, so the description needn't repeat it. Baseline 3 applies; the description adds no meaning beyond the schema.

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?

States a specific verb and resource ("Returns all money movement groups"), so the basic action is clear. However, it does nothing to distinguish this tool from close siblings such as getMoneyMovementGroupsByMonth, getMoneyMovements, or getMoneyMovementsByMonth, leaving the scope ambiguous.

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?

There is no guidance on when to use this tool versus its month-scoped or movement-level siblings. The agent must infer from the name alone that this returns the unfiltered group list.

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