Skip to main content
Glama

BRAINIAC Financial Schedule & Credit Calculations

Simulate repayment waterfall

fintech_repayment-waterfall-simulate

Allocate available cash across caller-supplied debt facilities by contractual priority and bucket order (fees, arrears, interest, principal). Returns step-by-step intermediate calculations. No bank account is accessed. Price $0.04 USDC. POST /api/v1/fintech/repayment-waterfall-simulate. Unpaid calls return 402 and do 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": {
      "available_cash": "<available_cash>",
      "currency": "<currency>",
      "facilities": "<facilities>"
    },
    "name": "fintech_repayment-waterfall-simulate"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyYes
facilitiesYes
available_cashYes
default_payment_orderNo

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?

With no annotations supplied, the description carries the full burden and does substantial work: it discloses that no bank account is accessed (no external side effects), that it returns intermediate calculations, that the call costs $0.04 USDC, and that unpaid calls fail with 402 without running. It stops short of stating whether the simulation persists anything or how errors other than 402 behave.

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?

The core mechanic is front-loaded in the first sentence and the following sentences each add a distinct operational fact (return shape, safety scope, price, transport, failure mode). The endpoint and price lines are terse and earn their place, though the mix of computation semantics with commercial/transport details makes it slightly list-like rather than prose.

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?

For a 4-parameter simulation tool with no annotations and no output schema, the description covers purpose, non-side-effect, return style and payment failure mode. The remaining gap is input preparation detail — how amounts are denominated and how the two payment-order fields interact — which matters given 0% schema coverage.

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 0%, so the description must compensate, and it partially does: it establishes that facilities are caller-supplied, that 'priority' is contractual ordering, and it enumerates the bucket vocabulary (fees, arrears, interest, principal) that maps to payment_order and default_payment_order. It says nothing about the relationship between per-facility payment_order and default_payment_order, the units of the integer amounts (minor units? cents?), or how interest_rate_bps relates to accrued_interest.

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?

States a specific verb and resource ('Allocate available cash across caller-supplied debt facilities') plus the mechanism (contractual priority and bucket order), so an agent knows exactly what computation happens. It never acknowledges the fintech siblings (covenant headroom, dilution, schedule risk), so the boundary against the nearest alternative is left to inference.

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?

'No bank account is accessed' and 'Returns step-by-step intermediate calculations' imply this is a pure what-if simulation, which steers usage. There is no explicit when-to-use statement, no statement of what inputs must be prepared beforehand (e.g. that facilities must be supplied by the caller rather than fetched), and no named alternative for the same 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