Skip to main content
Glama

Cash Coach AI

View spending by subcategory

subcategory_spending
Read-onlyIdempotent

Read one category’s subcategory amounts for an explicit month/year.

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>",
      "category": "<category>"
    },
    "name": "subcategory_spending"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
monthYes
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds that the period must be explicit (no defaults or ranges) and that results are scoped to a single category, but says nothing about return shape, ordering, or behavior for categories without subcategories.

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?

One tight sentence with the scope constraint front-loaded and no filler. It could still add a clause on category identifier format without becoming bloated.

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 three-parameter read-only lookup with full annotation coverage and no output schema, the definition supplies enough to call it correctly. Minor gaps remain around category identifier form and result ordering.

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 0%, so the description must carry the load. It does reference all three inputs conceptually and clarifies that month and year are supplied separately and explicitly, but it never says whether 'category' is a name or an ID, nor how month is numbered—both of which the raw schema only partially resolves.

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 (read) plus resource (subcategory amounts) and scope (one category, explicit month/year). An agent can infer this is a per-category drill-down rather than a total, though it never names category_spending as the contrasting sibling.

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?

The phrase 'for an explicit month/year' implies when the tool applies (single-period lookups, not ranges), but there is no explicit when-to-use vs. when-not, and no alternative tool is named for range or all-category queries.

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