Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_money_movements

Read-only

Lists money moved between budget categories, newest first, including category names, to review assigning or reassigning funds. Filter by month or plan and paginate with limit/offset.

Instructions

List money moved between categories (assigning or reassigning funds), newest first, with category names.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return.
monthNoOnly this month ('current', 'YYYY-MM').
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.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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 useful context beyond that: results are ordered newest-first and include resolved category names, which is output enrichment not visible in the annotations. It says nothing about pagination, volume, or what an empty result means, though the schema's offset description partially covers paging.

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 tightly written sentence with the resource statement front-loaded and no filler. The trailing 'with category names' is slightly compressed (it means names are resolved in the response) but is not wasteful.

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 a full output schema, complete schema descriptions, and covering annotations, the description only needs to orient the agent — which it does. The one remaining gap is the relationship to the movement-groups sibling, which an agent may not resolve from this text alone.

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%, so limit, month, offset and plan_id are all documented in the schema, including that plan_id comes from ynab_list_plans and that offset should use next_offset from a prior call. The description adds no parameter-level meaning, so the baseline 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 ('List money moved between categories') and even defines the domain term with a parenthetical ('assigning or reassigning funds'), so an agent knows exactly what record type is returned. It stops short of differentiating this from the sibling ynab_list_money_movement_groups, which is a closely related listing tool.

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?

Use is only implied by 'List' and the notion of category-to-category fund movement; there is no explicit when-to-use statement, no exclusion, and no pointer to ynab_list_money_movement_groups or ynab_list_transactions as alternatives. An agent can infer the use case from the domain wording, but nothing routes it away from similar list tools.

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