Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_plan_overview

Read-only

Summarize a YNAB plan by returning account balances, net worth, and counts of categories, payees, and transactions for a selected or default plan.

Instructions

Summarize a whole plan: account balances, net worth and how many categories, payees and transactions it has. Uses YNAB's full plan export (refreshed by delta), but returns only totals and counts. For details use the list_* tools.

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_get_plan_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful non-annotation detail: the data comes from YNAB's full plan export, refreshed by delta, and only totals and counts are returned, hinting that the underlying fetch is heavyweight. It stops short of stating cost or latency implications explicitly.

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?

Two sentences, front-loaded with the returned content before the implementation note and the routing hint. No filler, though the phrase "how many categories, payees and transactions it has" could be tightened to "entity counts" without losing meaning.

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?

With an output schema present, the description does not need to explain return structure, and annotations cover safety; the remaining payload is scope, behavior, and alternatives, all of which are addressed. Only marginal gaps remain, such as whether the export cost or refresh recency affects call timing.

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 coverage is 100% and the single optional plan_id already documents its source (ynab_list_plans) and the omit-to-use-default behavior. The description adds nothing about the parameter, which is acceptable given the schema does the work, so the baseline of 3 applies.

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

Purpose5/5

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

States a specific verb (summarize) and resource scope (a whole plan) and enumerates exactly what is returned: account balances, net worth, and counts of categories, payees, and transactions. The closing note that details live in the list_* tools separates it from the many ynab_list_* and ynab_get_* siblings without needing the schema.

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?

Gives an explicit use case (aggregate overview of a plan) and an explicit exclusion with an alternative ("For details use the list_* tools"). The alternative is given as a wildcard family rather than a single named sibling, which is slightly less precise but leaves no ambiguity about when this tool is wrong.

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