Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_months

Read-only

Lists YNAB budget months newest first with income, assigned, activity, Ready to Assign, and age of money for month-over-month trend analysis.

Instructions

List budget months (newest first) with income, assigned, activity, Ready to Assign and age of money. Good for month-over-month trends.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return.
offsetNoRows to skip (use next_offset from a prior call).
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
since_monthNoEarliest month to include ('YYYY-MM').
until_monthNoLatest month to include ('YYYY-MM').

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/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's genuinely additive behavior claim is the ordering ("newest first"); the enumerated fields (income, assigned, activity, Ready to Assign, age of money) add little because an output schema already exists. Pagination behavior is left to 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.

Conciseness5/5

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

Two short sentences, zero filler, with the resource and its default ordering front-loaded before the use-case hint. Nothing is repeated and nothing is wasted.

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?

For a read-only filtered-list tool with all-optional parameters, an output schema, and 100% schema coverage, the description covers purpose, defaults (newest first), and content. Slightly more on how the date-range parameters interact with the row limit would make it fully complete.

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%, with limit, offset, plan_id, since_month and until_month each documented in-schema, so the baseline is 3. The description adds no syntax or semantics (e.g., how since_month/until_month interact with the default limit of 12) beyond what the schema states.

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?

Specific verb and resource ("List budget months") plus the metric content it returns, so the agent knows it is a monthly-summary list rather than a single-month fetch. It does not explicitly name the boundary against ynab_get_month, relying on the list/get distinction being self-evident.

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?

"Good for month-over-month trends" implies a usage context but gives no explicit when-to-use/when-not or named alternative such as get_month for a single month. Guidance is implied rather than stated.

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