Skip to main content
Glama

Balance forecast

get_forecast
Read-onlyIdempotent

Projected balance of the accounts included in the forecast, month by month (income, expenses, end-of-month balance), the lowest projected balance and its date, accounts that go negative, and debts (what the user owes / is owed). Up to 6 months on the free plan and 60 with Cuéntamo Más; beyond the plan, only whether the balance goes negative and roughly when.

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
bookNoAccount book id (from list_books). Optional if the user has only one.
monthsNoMonths ahead (default 6).

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 declare readOnlyHint=true and destructiveHint=false, so safety is covered, but the description adds genuinely non-obvious behavior: the horizon is plan-gated at 6 months free vs 60 with Cuéntamo Más, and beyond the plan the tool degrades to only a yes/no negative flag plus approximate timing. That degradation caveat is important and appears nowhere in the schema or annotations.

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?

A single front-loaded sentence that leads with the primary output (projected balance month by month) before enumerating secondary outputs and the plan caveat. It is dense but every clause carries information; a semicolon-separated list might scan slightly faster than the trailing clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 does the work of listing returned fields, which it handles well. However, for a forecasting tool it omits how assumptions are formed (whether scheduled/recurring transactions are included) and gives no sense of precision or units, leaving a meaningful gap for an agent interpreting results.

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 100%, so both parameters are already documented, giving a baseline of 3. The description adds only indirect meaning about the months parameter via the plan horizon, but does not clarify the default of 6, the maximum of 60, or what book selection means when omitted.

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?

Names a specific verb and resource ("Projected balance of the accounts included in the forecast") and enumerates the exact outputs: monthly income/expenses/end-of-month balance, lowest projected balance and its date, accounts going negative, and debts. This clearly separates it from siblings like get_month_summary or how_much_can_i_spend, which are retrospective or spending-cap oriented.

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 implied by the output enumeration rather than stated: an agent can infer it answers forward-looking balance questions, but there is no explicit when-to-use or when-not clause. No sibling is named as an alternative, and nothing says how it relates to confirm_forecast or how_much_can_i_spend, which are plausible competing choices for a similar question.

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