Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Smoothed spending

get_smoothed_spending
Read-onlyIdempotent

Compare raw and averaged monthly costs from configured rules to see whether an expensive month was truly unusual, spreading lumpy categories over a trailing window.

Instructions

Raw against smoothed monthly cost for each configured smoothing rule, which spreads a lumpy category (travel, annual insurance) over a trailing window. Use it to tell whether an expensive month was genuinely unusual. Empty when no rules are configured.

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

Input Schema

NameRequiredDescriptionDefault
months_backNo

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 read-only, idempotent, closed-world, non-destructive behavior, so safety is covered. The description adds real value beyond that: it explains the trailing-window smoothing mechanism and the empty-result condition when no rules exist, which is the main surprise an agent could hit. Return shape is not described, keeping it short of a 5.

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?

Two tight sentences: the mechanism first, the decision use second, plus the empty-state caveat. No filler and nothing buried at the end.

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?

With no output schema, the description should convey more about what comes back (per-rule raw vs smoothed series, granularity). It covers the concept, the use case, and the empty case, but omits both the return structure and any explanation of its only parameter.

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?

The single parameter months_back has 0% schema description coverage, so the description carries the full burden — yet it never mentions the parameter, its default of 12, or the 1-60 bounds. 'Trailing window' gestures at the concept but does not tell the agent that months_back sets it.

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 exact resource (raw vs smoothed monthly cost per smoothing rule) and explains the underlying concept in a parenthetical, so an agent knows this is the smoothing-aware view rather than plain spend. It does not name the sibling it contrasts with (get_spending), but the 'raw against smoothed' framing effectively delineates it.

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?

'Use it to tell whether an expensive month was genuinely unusual' gives a concrete decision context, and 'Empty when no rules are configured' warns when it is useless. No explicit when-not or named alternative, but the usage condition is clear enough to route correctly.

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