Skip to main content
Glama

Get Cash Flow Forecast

get_cash_flow_forecast
Read-onlyIdempotent

13-week cash-flow forecast. Returns current bank balance, projected weekly inflows/outflows/running balance for the next 13 weeks, projected low point, recurring patterns detected from history, outstanding invoices expected to clear, recurring invoice projections, and tax deadlines that could draw cash. Also returns tax_set_aside: the tax to keep aside (sales tax owed, the running company tax balance on this year's profit less tax already paid, the recommended set-aside rate and amount when one is saved, and for a company with tax instalments the next instalment, the schedule paid so far against due so far, the balance-due date and the basis). Use when the user asks about cashflow, runway, "can I afford X", "when will I run out", how much to set aside for tax, or their next tax instalment, or wants to plan ahead. Quote the figures it returns; never work out an instalment yourself.

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

Input Schema

NameRequiredDescriptionDefault
companyNoWhich company to read, by name or id, when the account has more than one (see list_companies). Leave it out to use the only company, or the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world safety, so the description's contribution is the return-content inventory plus the important instruction 'Quote the figures it returns; never work out an instalment yourself.' That is real added value, though it could also have said something about currency, staleness, or data freshness.

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?

Purpose is front-loaded, but the body is a single enormous run-on sentence stacking a dozen return fields, followed by a deeply nested clause describing tax_set_aside components. Every item earns its place given there is no output schema, yet the structure makes it hard to scan.

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 describing returns and does so exhaustively, including the tax set-aside sub-structure and the no-manual-calculation rule. A minor gap remains around freshness/currency expectations and the company scoping parameter.

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?

There is only one optional parameter and the schema describes it fully at 100% coverage, including the pointer to list_companies and multi-company default behaviour. The description adds nothing about it, so the baseline of 3 applies.

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 opens with a specific resource and scope ('13-week cash-flow forecast') and immediately enumerates the outputs, so an agent can distinguish it from backward-looking siblings like get_balance or get_financial_snapshot 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 lists concrete trigger phrasings ('cashflow', 'runway', 'can I afford X', 'when will I run out', tax set-aside, next instalment, planning ahead) and adds an explicit behavioural rule not to compute instalments manually. It stops short of naming an alternative tool or stating when not to use it.

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.