Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_plans

Read-only

Lists YNAB plans with IDs, currency, and month range so you can find a plan_id before using other budget tools; optionally includes each plan's accounts.

Instructions

List the user's YNAB plans (budgets) with ids, currency and month range.

Call this first if you need a plan_id; most tools default to the configured plan.

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

Input Schema

NameRequiredDescriptionDefault
include_accountsNoAlso list each plan's accounts (larger output).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds non-obvious context: what the listing contains and the fallback behavior of 'most tools default to the configured plan', which shapes downstream calls; it does not mention rate limits or result caching.

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

Conciseness5/5

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

Two short sentences, front-loaded with the action and result fields, followed immediately by the routing guidance. No filler wording or repetition of schema content.

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

Completeness4/5

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

An output schema exists, so return values need not be spelled out, and the single optional parameter is fully documented. For a simple read-only list tool this is essentially complete; only minor operational details (pagination, freshness) are 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 optional parameter with 100% schema description coverage ('Also list each plan's accounts (larger output)'), so the schema already explains the cost tradeoff. The description adds nothing further about include_accounts, which is acceptable at baseline 3 when the schema does the work.

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?

States a specific verb and resource ('List the user's YNAB plans (budgets)') and clarifies the plan/budget terminology, plus names the returned fields (ids, currency, month range). It does not explicitly differentiate itself from the get_plan_overview / get_plan_settings siblings, so the agent must infer that this is the enumeration tool.

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

Usage Guidelines4/5

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

'Call this first if you need a plan_id' gives a clear triggering condition, and 'most tools default to the configured plan' tells the agent it can skip this call when no explicit plan_id is needed. It stops short of stating an explicit when-not-to-use rule or naming the alternatives that accept a plan_id.

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