Skip to main content
Glama
make-cents-please

make-cents-please

by hopkeno

ynab_get_category

Read-only

Retrieves one YNAB category's assigned, activity, available, and goal details for the current or a specified month, with optional plan selection.

Instructions

Get one category's assigned, activity, available and goal details, optionally for a specific month.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category_id": "<category_id>"
    },
    "name": "ynab_get_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthNoMonth for the amounts ('current', 'YYYY-MM'). Omit for current.
plan_idNoPlan (budget) id from ynab_list_plans. Omit to use the configured default plan.
category_idYesCategory id from ynab_list_categories.

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 elsewhere. The description's added value is the month-scoping behavior and the specific numeric fields returned, but it says nothing about rate limits, auth, or error cases, which keeps it at an adequate-but-thin level.

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 front-loaded sentence with the resource, the returned fields, and the optional month qualifier; nothing is wasted and nothing essential is buried.

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 describing return values and full parameter descriptions, the definition only needs to establish what the tool fetches, which it does. A brief pointer to the sibling list tool would have closed the last gap.

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 month formats ('current', 'YYYY-MM'), the default-plan fallback for plan_id, and the provenance of category_id all documented in the schema. The description's "optionally for a specific month" merely echoes the schema, 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 uses a specific verb and resource ("Get one category") and enumerates the data returned: assigned, activity, available and goal details. That clearly separates it from ynab_list_categories, though it never names that sibling explicitly, so the differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

The only contextual cue is "optionally for a specific month"; there is no statement of when to reach for this tool over ynab_list_categories, no prerequisites, and no note about needing an existing category id. The agent must infer usage entirely from the name and schema.

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