Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Run a what-if scenario

run_scenario
Read-onlyIdempotent

Test a one-off purchase or recurring financial change to see projected net worth, savings rate, and goal dates before and after—without a verdict.

Instructions

The tool for 'can I afford X' and 'what if X'. Applies one hypothetical change and reports three consequences: projected net worth with its delta and low point, the ongoing savings rate before and after, and every goal's landing month before and after with the pool it draws on. Consequences only, never a verdict. A one-off does not change the ongoing savings rate, and the result says so instead of giving a delta.

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": {
      "kind": "<kind>",
      "amount_eur": "<amount_eur>",
      "month": "<month>"
    },
    "name": "run_scenario"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes'once' for a single purchase or windfall; 'monthly' for a recurring change.
monthYesYYYY-MM: the month a one-off lands or a recurring change starts.
amount_eurYesSIGNED euros. Negative is a cost (a purchase, a rent rise); positive is money kept or gained.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it specifies the three reported consequences in detail (net worth delta and low point, savings rate before/after, per-goal landing months with source pool). The edge case 'a one-off does not change the ongoing savings rate, and the result says so instead of giving a delta' pre-empts a predictable misreading of the output.

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?

Front-loaded with the question it answers, then the three outputs, then the scope caveat — no filler sentences. Denser than ideal in the third sentence, where the three consequences are packed into one long clause, but every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must carry the return-shape burden, and it does — enumerating all three consequence categories and their before/after structure. With safety behavior covered by annotations and parameters fully documented, an agent has what it needs to call this correctly.

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 coverage is 100%, including enum values, the YYYY-MM pattern, and the sign convention for amount_eur, so the schema already carries parameter meaning. The description adds only indirect semantics (one-off vs recurring behavior is mentioned), which is the baseline for full schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — 'applies one hypothetical change and reports three consequences' — and names the exact questions it answers ('can I afford X', 'what if X'). The three enumerated outputs let an agent distinguish it from the reporting/read siblings without opening the schema.

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 'afford X / what if X' framing gives a clear situation for use, and 'consequences only, never a verdict' signals when it is the wrong tool (i.e. when the agent wants a target or answer rather than impact). It does not name the obvious alternative (what_would_it_take) explicitly, so the routing is left slightly implicit.

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