Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Spend history by category

get_spend_history
Read-onlyIdempotent

Analyze spending by category across trailing complete months to surface median monthly amounts, min/max/latest values, and zero-filled month counts that expose lumpy costs and potential cut areas.

Instructions

Where a cut could come from: for each category over the trailing complete months, the MEDIAN month with its min, max and latest, zero-filled so monthsPresent shows how lumpy it is. Median, not mean: one unusual month must not suggest headroom that is not there. The server does not decide what is realistic to cut; that judgement is the user's.

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": "get_spend_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoTrailing complete months.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, yet the description still adds real substance: the aggregation is a median by design so one outlier month cannot fake headroom, months are zero-filled, and monthsPresent exposes lumpiness. That is behavior an agent could not infer from annotations alone.

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?

Three tight sentences, front-loaded with the purpose and then the median rationale, with no filler. Minor cost: 'zero-filled so monthsPresent shows how lumpy it is' is dense jargon that requires a second read, and monthsPresent is an output field never introduced.

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 no output schema, the description carries the return-value burden and does so: it names the per-category container and the stats returned (median month, min, max, latest, monthsPresent). What 'min, max and latest' actually measure (monthly spend values) is left implicit, which is the only real gap for a single-parameter read tool.

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?

Only one parameter, and schema description coverage is 100% with 'Trailing complete months' plus min/max/default bounds already documented. The description echoes the phrase 'trailing complete months' but adds no new meaning about how the window interacts with zero-filling, 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 states a concrete retrieval: per-category, over trailing complete months, the MEDIAN month with min, max and latest, zero-filled. That is specific enough for an agent to know this is a categorical spend-history/statistics tool, not a raw ledger. It does not explicitly contrast itself with siblings like get_spending or get_smoothed_spending, so it stops 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 Guidelines3/5

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

"Where a cut could come from" implies the use case (budget-reduction analysis) but never states when to pick this over get_spending or get_smoothed_spending, nor any exclusions. The closing line that the server does not decide what is realistic to cut is a helpful framing note rather than routing guidance.

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