Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_list_money_movement_groups

Read-only

List YNAB money movement groups newest first to review assign and move actions, with optional month, plan, limit, and pagination filters.

Instructions

List groups of money movements (one group per assign/move action), newest first.

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

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.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 safety and network scope are covered. The description adds two genuine behavioral facts beyond that: results are grouped one-per-assign/move action, and ordering is newest-first. It says nothing about pagination or how groups relate to their member movements, but the output schema covers return structure.

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?

A single sentence with zero filler, front-loading the verb and resource before the clarifying parenthetical and ordering detail. Nothing could be removed without losing information.

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 full schema coverage, an output schema, and read-only annotations, the description covers the essentials: what a group is and how results are ordered. The remaining gap is the absence of any pointer to ynab_list_money_movements for the ungrouped view, which moderately complicates tool selection among list siblings.

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, month, offset and plan_id each documented in the schema itself, so the baseline is 3. The description adds no parameter-level meaning (e.g., how month interacts with grouping), leaving the schema to do all 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 groups of money movements') and adds real semantic content in the parenthetical ('one group per assign/move action'), which tells the agent this returns grouped entities rather than raw movements. It does not name the sibling ynab_list_money_movements, so the group-vs-flat distinction is implied rather than explicit.

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: the grouping note hints at when this is preferable to listing individual movements, but there is no explicit when-to-use, when-not-to-use, or named alternative. Ordering ('newest first') gives context but no selection guidance.

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