Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Plan

get_plan
Read-onlyIdempotent

Retrieve a personal finance plan with goal targets, progress and pace, liquid and investment pool balances, income/spend/savings rates, and a 12-month net worth forecast with planned items.

Instructions

Where this is heading: every goal's target, progress, pace, required pace and projected landing month, the liquid and investment pools and the pace feeding each, the trailing income, spend and savings rate, a 12-month net worth forecast and the planned items behind it with their confidence. For 'what if', use run_scenario.

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

Input Schema

NameRequiredDescriptionDefault
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

A4.1/5.0
Behavior4/5

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

The supplied annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so the description need not restate safety. It adds meaningful scope detail about what the plan returns, including forecasts and confidence on planned items, though it does not discuss data freshness or computation basis. The detail parameter's behavioral effect is documented in the schema rather than the description.

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?

The description is a dense single sentence enumerating relevant outputs plus a short routing sentence, with almost every clause naming concrete return elements. It is informative rather than padded, though the opening phrase 'Where this is heading' is less scannable than a direct action verb.

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?

Because there is no output schema, the description usefully enumerates the plan contents an agent will receive and redirects scenario work to run_scenario. It is sufficiently complete for a one-parameter read-only tool. A brief note on data basis or how it relates to forecast-only views would make it stronger.

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?

The sole detail parameter is fully documented in the schema: summary keeps headline figures and drops per-day/per-month series, while full returns everything. The description never mentions this parameter, so it adds no meaning beyond the schema. With 100% schema description coverage, the baseline score of 3 is appropriate.

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?

The description names the plan resource and enumerates the exact outputs: goal targets, progress, pace, projected landing months, liquid and investment pools, trailing income/spend/savings, a 12-month net worth forecast, and planned items with confidence. It also distinguishes the tool from run_scenario for what-if analysis. An agent can identify the tool's purpose 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?

It gives one explicit routing rule: for 'what if' analysis, use run_scenario. That is a clear exclusion, but it does not explain when to choose this comprehensive plan view over narrower sibling tools such as forecast-only or overview views. The guidance is useful but not exhaustive.

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