Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Net worth forecast

get_forecast
Read-onlyIdempotent

Projects net worth month by month from next month using trailing income and spending averages plus planned items, and explains the resulting figures without recalculating them.

Instructions

Projects NET WORTH month by month from next month: trailing average income and spend plus planned items (bills still due this month fold into the first row). Explain the numbers, do not recompute them. Investment growth is not modelled and transfers to investments leave net worth unchanged. Planned items count at face value whatever their confidence; endNetWorthWithoutTentativeEur is the end figure without tentative ones.

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

Input Schema

NameRequiredDescriptionDefault
horizon_monthsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and closed-world traits, yet the description adds substantive modeling caveats: no investment growth, transfers to investments are net-worth-neutral, tentative planned items count at face value, and bills still due this month fold into the first row. That is real behavioral disclosure an agent would otherwise get wrong. It stops short of describing the per-row shape of the projection.

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?

Roughly fifty words across four tight sentences, with the core projection statement front-loaded and each subsequent sentence carrying a distinct caveat (planned items, investment exclusion, tentative figures). No filler or restatement of the name and title.

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 in place, the description does well to define endNetWorthWithoutTentativeEur and to flag which factors are and are not modeled. What remains thin is the input side — the horizon parameter and what a row of the forecast contains — but for a single-optional-parameter read tool this is close to sufficient.

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 description coverage is 0%, so the single horizon_months parameter (default 12, max 60) is undocumented anywhere. The description conveys month-by-month granularity starting next month, which implies the horizon conceptually, but never names the parameter, its default, or its 60-month cap. Partial compensation only.

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 with scope: 'Projects NET WORTH month by month from next month.' The starting point and granularity distinguish it from a static overview or a plan view, and the modifier 'NET WORTH' rather than spend or balance makes the output target unambiguous.

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?

The description gives an output-handling rule ('Explain the numbers, do not recompute them') but nothing on when to choose this over run_scenario or what_would_it_take, which are the obvious projection-adjacent siblings. Guidance is implied by the word 'forecast' rather than stated as a selection rule.

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