Skip to main content
Glama
YNAB MCP Server

YNAB MCP Server

by rgarcia

Getplans

getPlans

Retrieve YNAB plans with summary information and optionally include their accounts for budget review and comparison.

Instructions

Returns plans list with summary information

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "getPlans"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_accountsNoWhether to include the list of plan accounts

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 supplied, the description carries the full behavioral burden, yet it discloses only that results are a 'summary' list. It says nothing about whether the call is read-only, how large the result can be, ordering, pagination, or how 'summary information' differs from the full plan objects returned elsewhere.

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?

One short, front-loaded sentence with no filler. It is efficient, and its brevity is appropriate for a simple list endpoint, though the terseness leaves little substance.

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

Completeness3/5

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

This is a simple read tool with one optional boolean parameter and no output schema, so the description should at minimum characterize the returned 'summary information' and whether accounts are excluded by default. It gestures at the return shape but does not specify it, leaving a modest but real gap.

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 single optional parameter include_accounts is documented in the schema itself. The description adds no meaning beyond that, so the baseline of 3 applies.

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?

The description names a specific verb and resource ('Returns plans list') and adds a scope hint ('with summary information'), which distinguishes it from the more granular siblings getPlanMonth, getPlanMonths, and getPlanSettingsById. It stops short of explicitly stating how it differs from those siblings, so it is clear rather than exemplary.

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, no prerequisites, and no named alternative. An agent must infer from sibling names alone whether to call getPlans or getPlanMonths, which the definition never addresses.

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