Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Spending for a month

get_spending
Read-onlyIdempotent

Breaks down a month's spending by category and need level, comparing it with a normal month and the same month last year to explain why that month was expensive.

Instructions

One month's spending by category and by must/need/want, against a normal month (the median of the preceding complete months) and the same month last year, plus that month's planned bills. Answers 'why was last month expensive'. Transfers are excluded.

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

Input Schema

NameRequiredDescriptionDefault
monthNoYYYY-MM. Defaults to the current month.
detailNosummary (default) keeps headline figures and drops per-day and per-month series. full returns everything.summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, yet the description still adds real value by defining the baseline methodology ('the median of the preceding complete months') and the exclusion of transfers. It stops short of describing granularity limits or what happens when no prior months exist.

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 dense sentence that front-loads the core output and appends the comparison baselines as a parenthetical. It is efficient, though the nested clauses take some parsing.

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 burden of explaining return content, and it does so by listing the breakdowns, comparisons, and planned bills. The remaining gap is edge-case behavior, such as partial months or missing history.

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?

Both parameters are fully documented in the schema, including the YYYY-MM pattern, the default to the current month, and the summary/full distinction. The description adds no extra meaning about either parameter, 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?

Names the specific resource and its breakdowns ('one month's spending by category and by must/need/want'), the comparison baselines, and the added planned bills, so an agent knows exactly what comes back. It does not differentiate itself from siblings such as get_smoothed_spending or get_spend_history, 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 Guidelines4/5

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

The phrase 'Answers "why was last month expensive"' gives a concrete use case, and 'Transfers are excluded' scopes the data. No alternative tool is named and no when-not-to-use condition is stated, so routing still requires inference.

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