Skip to main content
Glama
cashcast-mcp

cashcast-mcp

What would it take

what_would_it_take
Read-onlyIdempotent

Calculates the monthly gap to reach a financial goal by a target month and shows how spending cuts or extra income close it.

Instructions

The inverse of run_scenario, for 'what would it take to hit X by Y'. Returns ONE number, the monthly gap between the pace the date needs and the pace being run, plus every goal's landing month once it is closed. A spending cut and extra regular income close it one to one: pass what the user can already find and read residualGapEur. Extra income only helps if it is not spent; say so. When the outcome is not a gap (no_lever, date_passed, on_track) report the reason, not a number.

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": {
      "goal": "<goal>",
      "by_month": "<by_month>"
    },
    "name": "what_would_it_take"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalYesGoal name as get_plan reports it.
by_monthYesYYYY-MM, the month to land on.
assume_spend_cut_eurNoMonthly spending cut the user says they can make.
assume_extra_income_eurNoMonthly extra regular income the user says they can find.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/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 adds substantial context beyond them: it returns exactly ONE number, also returns every goal's landing month, and enumerates the non-gap outcome codes (no_lever, date_passed, on_track) that must be reported as reasons instead of numbers. It also flags the semantic caveat that extra income only helps if unspent.

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-loads the core purpose and return shape, then layers usage and edge-case handling. Dense but every sentence carries information; minor density in the lever-explanation sentences keeps it from a 5.

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?

With no output schema, the description carries the burden of explaining return values and does so fully: the single gap number, the per-goal landing months, and the reason codes for non-gap outcomes. Nothing an agent needs to call and interpret the tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that a spending cut and extra regular income close the gap one-to-one, that the agent should pass what the user can already find, and that residualGapEur is the value to read. This goes beyond the schema's field descriptions.

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 ('what would it take to hit X by Y') and explicitly positions itself as the inverse of run_scenario, so an agent can distinguish it from that sibling without opening either schema. It also names the single return value (monthly gap).

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?

Gives clear routing context by naming run_scenario as the inverse and describing the question shape it answers. It also tells the agent how to use the levers (pass what the user can find, read residualGapEur) and to report the reason rather than a number for non-gap outcomes. It stops short of explicit when-not-to-use conditions beyond the inverse framing.

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