Skip to main content
Glama

Cash Coach AI

Compare spending by category

category_spending
Read-onlyIdempotent

Read signed category aggregates for an explicit month/year, including past months retained by Cash Coach.

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": {
      "month": "<month>",
      "year": "<year>"
    },
    "name": "category_spending"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that past months retained by Cash Coach are available, which is genuinely useful context beyond the annotations, but it does not explain the sign convention of 'signed' amounts, retention limits, or timezone handling.

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 well-formed sentence with the resource and scoping constraint front-loaded and no filler. Slight deduction because 'signed category aggregates' is dense jargon that could be unpacked in the same space.

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?

For a simple two-parameter read tool with rich annotations and no output schema, the description covers the core call. However, with no output schema the description should hint at what comes back — what a 'category aggregate' contains, whether zero-spend categories appear, and unit/currency — none of which is addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the two parameters (month, year) rely entirely on the description and bare integer constraints. The description only asserts they must be 'explicit' and adds no format, range, or interpretation guidance beyond what the schema's min/max already conveys.

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 ('Read signed category aggregates') scoped to an explicit month/year, which is clearer than the bare title. The term 'signed category aggregates' is somewhat jargon-y and does not distinguish this from sibling tools like subcategory_spending or daily_spending, so it falls short of a 5.

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?

No statement of when to choose this over daily_spending, subcategory_spending, or spending_history. The only usage cue is 'explicit month/year,' which implies both parameters must be supplied rather than a relative period, but no alternative is named and no exclusions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources