Skip to main content
Glama
cashcast-mcp

cashcast-mcp

Accounts

get_accounts
Read-onlyIdempotent

Retrieve each account's balance and type, cash and investment totals, and year-to-date income, spending, invested amount, and savings rate through the last complete month.

Instructions

Observed state: each account's balance and type, cash and investment totals, and the year to date income, spend, amount invested and savings rate. The ytd figures run to the LAST COMPLETE MONTH (ytdWindow states it), so they differ from get_overview's yearSoFar by the current month. That is two windows, not a discrepancy.

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

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

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), so the description earns credit for adding the non-obvious behavior: YTD figures stop at the last complete month, as reported by ytdWindow, and legitimately differ from get_overview's yearSoFar. Warning that this is 'two windows, not a discrepancy' preempts a plausible misinterpretation. It stops short of describing ordering or account coverage.

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?

Two tight sentences, front-loaded with the payoff (what state is observed) and then the caveat that prevents misreading. The 'Observed state:' lead is slightly cryptic but compact, and nothing is redundant.

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, the description carries the burden of conveying return content and does so at a useful level of detail, plus the window caveat. Minor gaps remain around result shape (flat list vs nested accounts) and whether accounts with zero activity appear, but nothing essential to calling it correctly is missing.

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 is fully documented in the schema, including the enum values and what summary drops, so the description need not repeat it. The description's field list does not map back to summary vs full tradeoffs, so it adds no meaning beyond the schema; baseline 3 applies.

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

Purpose4/5

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

The description enumerates the concrete payload (balance and type per account, cash and investment totals, YTD income/spend/invested/savings rate), which lets an agent recognize this as the account-level observed-state tool. It distinguishes itself from get_overview by contrast, though it never states a plain 'returns the list of accounts' framing.

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?

Guidance is implied rather than stated: the get_overview comparison tells the agent these two return related but differently-windowed figures, so it should use both rather than substitute one. There is no explicit 'use this when you need per-account detail instead of household totals' statement, and no mention of when summary vs full is appropriate.

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