Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_month

Read-only

Retrieve a single YNAB budget month to view income, assigned, activity, Ready to Assign, age of money, and per-category assigned, activity, and available balances.

Instructions

Get one budget month: totals (income, assigned, activity, Ready to Assign, age of money) plus per-category assigned/activity/available for that month.

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

Input Schema

NameRequiredDescriptionDefault
groupNoOnly categories whose group name contains this text.
monthNoMonth as 'current', 'YYYY-MM' or 'YYYY-MM-01'.current
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
include_zeroNoInclude categories with nothing assigned, spent or available.
only_overspentNoOnly categories with a negative available balance.
include_categoriesNoSet False to return only the month totals.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/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 usefully enumerates the returned data (totals plus per-category breakdown), but says nothing about the absence of side effects, rate-limit behavior, or what an empty/closed month looks like — and an output schema already documents returns.

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?

A single front-loaded sentence with the resource named first and the returned fields itemized in a parenthetical. Nothing is redundant, though the enumerated field list is dense enough to read as a spec dump rather than prose.

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?

With six optional parameters, an output schema, and full annotations, the structured data carries most of the load, and the description supplies the output inventory. What it omits is routing guidance among siblings and the default behavior (current month, configured default plan), which an agent must read from the schema.

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 all six parameters carry their own descriptions (group filter, month formats, plan_id, include_zero, only_overspent, include_categories). The description adds no parameter-level meaning beyond what the schema provides, 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 gives a specific verb and resource ("Get one budget month") and enumerates exactly what comes back: month totals for income, assigned, activity, Ready to Assign and age of money, plus per-category assigned/activity/available. The word "one" implicitly distinguishes it from ynab_list_months, but no sibling is named, so the contrast is left to inference.

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

Usage Guidelines3/5

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

Usage is only implied: fetch a single month's detail rather than a list. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as ynab_list_months for enumerating months, and no mention that the default returns the current month with all categories included.

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