Skip to main content
Glama

BRAINIAC Accounting Schedules & Close

13-week direct cash-flow forecast

accounting-schedules_cash-flow-forecast-13w
Read-onlyIdempotent

Bucket receivables, payables and recurring cash items into Monday-start weeks and report closing cash versus a minimum. Price $0.04 USDC. POST /api/v1/accounting-schedules/cash-flow-forecast-13w. An unpaid call returns the x402 payment terms and does not run.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "openingCash": "<openingCash>",
      "weekStart": "<weekStart>"
    },
    "name": "accounting-schedules_cash-flow-forecast-13w"
  }
}

Input Schema

NameRequiredDescriptionDefault
payablesNopayables, array. Required.
recurringNorecurring, array. Required.
weekStartYesweekStart, string, date. Required.
minimumCashNominimumCash, integer, from -9007199254740991 to 9007199254740991. Required.
openingCashYesopeningCash, integer, from -9007199254740991 to 9007199254740991. Required.
receivablesNoreceivables, array. Required.

Output Schema

NameRequiredDescriptionDefault
weeksNoweeks. Array.
sourcesNosources. Array.
lowestWeekNolowestWeek. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-schema information: a $0.04 USDC price and the fact that an unpaid call returns x402 payment terms without executing, which is exactly the kind of cost/auth behavior an agent needs before invoking.

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?

Four short sentences, front-loaded with the core computation before price, endpoint and payment behavior. Every sentence carries information, though the raw POST path is arguably redundant with the tool name and adds little for an agent.

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 an output schema present, the description need not explain return values, and full schema coverage handles parameters. Combined with the disclosed pricing and payment-failure behavior, an agent has enough to call it correctly; only explicit alternative-routing guidance 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?

Schema description coverage is 100%, so the schema already documents all six parameters, including nested receivables/payables/recurring items and the delay fields. The description adds only indirect meaning — 'Monday-start weeks' hints at weekStart alignment and 'versus a minimum' clarifies minimumCash — which is modest value on top of a fully documented schema.

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 gives a specific verb and resource: it buckets receivables, payables and recurring cash items into Monday-start weeks and reports closing cash against a minimum. That is concrete enough to distinguish it from siblings like depreciation or lease schedules, though it never explicitly names an alternative or restates the 13-week horizon.

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 the described output (a weekly cash forecast versus a minimum threshold); there is no explicit when-to-use or when-not-to-use statement, and no guidance on choosing between this and other accounting-schedule tools. The payment note describes a runtime condition, not a usage guideline.

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