Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getplanmonths

getPlanMonths

Retrieves all months for a specified YNAB plan and can return only entities changed since a known server knowledge value.

Instructions

Returns all plan months

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

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.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does almost nothing with it. It does not confirm this is a read-only operation, does not mention pagination or result size, and says nothing about the incremental-sync behavior implied by last_knowledge_of_server (that detail lives only in the schema).

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 sentence with no filler and nothing to trim, so it is maximally concise. The problem is under-specification rather than verbosity: the single sentence leaves an agent without scope, ordering, or usage context.

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, no output schema, and no explanation of what a returned "plan month" contains, an agent cannot tell what it will receive or how to consume it. For a list endpoint that likely returns a collection plus server knowledge, the description is too thin to be self-sufficient.

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%, and the schema already documents both plan_id (including the "last-used" and "default" sentinels) and last_knowledge_of_server thoroughly. The description adds no meaning beyond that, which is acceptable given the schema's completeness, but it earns only the baseline.

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 plan months" states a verb and a resource, so the basic operation is identifiable. But it never explains what a plan month is (monthly budget snapshot vs. something else) and gives no cue distinguishing it from the sibling getPlanMonth, which presumably returns a single month. The purpose is plausible but underspecified.

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 when-to-use guidance at all: no mention of when to prefer this list operation over getPlanMonth for a single month, and no note about the delta-fetching pattern. The only hint an agent gets is the plural in the tool name.

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