Skip to main content
Glama

How much can I spend?

how_much_can_i_spend
Read-onlyIdempotent

How much the user can spend right now without breaking their forecast: a one-off amount, an extra monthly amount and a daily amount until the next expected income (spending.daily: amount, days, until; untilIncome=false means until the 1st of next month), with and without touching their emergency cushion (cushion_months of essential spending, 3 by default as in the app). Computed by Cuéntamo over the full 5-year horizon, also on the free plan. If the balance is forecast to go negative, says so (free plan: only roughly when, in years). Month values may be "now", "later" (beyond the free plan window) or null (not within the forecast).

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": "how_much_can_i_spend"
  }
}

Input Schema

NameRequiredDescriptionDefault
bookNoAccount book id (from list_books). Optional if the user has only one.
cushion_monthsNoMonths of essential spending to keep as emergency cushion (default 3).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's job is to add context. It does: the computation runs over a full 5-year horizon, works on the free plan, and on the free plan the negative-balance warning degrades to a rough year-level estimate — a real behavioral limitation an agent should know before answering. It stops short of describing response shape or precision/rounding beyond that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading clause is well front-loaded, but the rest collapses into one dense run-on sentence with nested parentheticals ("spending.daily: amount, days, until; untilIncome=false means...") that mix return-value documentation with input documentation. The content is largely relevant, but the structure makes it hard to parse.

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?

There is no output schema, so the description must carry the return semantics — and it does, naming the three spendable amounts, the until/untilIncome distinction, and the cushion comparison. The main gap is that the enumerated return fields are described ambiguously (the `untilIncome` reference) and no guidance is given on typical follow-up calls.

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 coverage is 100%, so baseline is 3. The description restates cushion_months semantics ("cushion_months of essential spending, 3 by default as in the app") in nearly the same words as the schema, and never mentions the `book` parameter. Worse, it introduces "untilIncome=false", a field that is not an input parameter at all, which muddies rather than clarifies parameter meaning.

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 specific verb+resource framing: "How much the user can spend right now without breaking their forecast," then enumerates the three amounts returned (one-off, extra monthly, daily until next income). This is clearly distinct from siblings like get_forecast or add_transaction, which the agent can rule out without opening a schema.

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?

Usage is only implied by "right now" and by the free-plan availability note; there is no explicit when-to-use statement or pointer to an alternative such as get_forecast for raw forecast data. An agent can infer the intent but receives no routing guidance or exclusions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources