Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Overview

get_overview
Read-onlyIdempotent

Get a full personal-finance snapshot: net worth, cash and investment split, monthly spend, bills due, savings rate, and goal progress with projected landing months.

Instructions

Start here for 'am I OK right now'. Net worth with its cash and investment split, this month's spend, what is left to spend and the bills still to come, the trailing savings rate, every goal's progress and projected landing month, the year so far and what a normal month looks like. Leads with contextNotes, the user's standing facts. yearSoFar runs to today and includes the current partial month, unlike get_accounts' ytd figures.

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

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/5.0
Behavior3/5

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

Annotations already establish the safe-read profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the bar is lower. The description adds real behavioral context: the response leads with contextNotes containing the user's standing facts, and yearSoFar's partial-month inclusion is a disclosure of calculation semantics rather than a repeat of annotations. It says nothing about response size or how the summary/full split affects payload volume, which would matter for a broad overview call.

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 selection cue is front-loaded ahead of the content catalog, which is the right ordering for a routing decision. The middle sentence is a long comma-spliced enumeration, but for an overview tool every listed figure corresponds to a distinct section an agent may need to know exists, so little is genuinely wasteful.

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 describing return content and does so thoroughly section by section, plus it flags the leading contextNotes field and a cross-tool caveat about date framing. For a zero-required-parameter overview tool, an agent has everything needed to call it and interpret the result.

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 single detail parameter has 100% schema description coverage with an enum whose semantics (summary drops per-day and per-month series, full returns everything) are already spelled out in the schema. The description never references detail, so it adds no meaning beyond that; per the high-coverage baseline this is a 3.

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?

Opens with a concrete selection cue ("Start here for 'am I OK right now'") and then enumerates exactly what the tool returns: net worth with cash/investment split, month spend, remaining-to-spend, upcoming bills, savings rate, goal progress, year-to-date and a normal-month baseline. It also distinguishes its own yearSoFar figures from get_accounts' ytd, so a sibling can be told apart without opening either 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?

"Start here" is explicit entry-point guidance for the overview use case, and the note that yearSoFar includes the current partial month while get_accounts' ytd does not tells the agent which one to prefer for which question. It does not state when to move on to siblings like get_forecast, get_plan or get_smoothed_spending, so the routing is only partly covered.

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