Skip to main content
Glama

BRAINIAC Financial Schedule & Credit Calculations

Audit financial schedule stress

fintech_schedule-risk-audit

Stress-test a caller-supplied loan schedule, cashflow stream, and payout list. Inflows move 7, 14, and 30 days later, outflows stay on their dates, and financing cost uses the supplied annual rate. The math stays in memory. This is not a credit decision. Price $0.04 USDC. POST /api/v1/fintech/schedule-risk-audit. Unpaid calls return 402 and do not run.

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": "fintech_schedule-risk-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNo
paymentsNo
cashflowsNo
milestonesNo
annual_rateNo
minimum_balanceNo
opening_balanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses date-shift behavior for inflows, fixed outflow dates, financing-cost treatment, in-memory computation, the $0.04 USDC price, the endpoint, and the 402 failure mode. It omits any description of the response shape, which is a notable gap given there is no output schema.

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 description is short and front-loaded, moving from purpose to mechanics to pricing and failure behavior. The telegraphic sentences carry no real waste, though the fragmented style sacrifices some readability.

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?

For a seven-parameter financial simulation tool with no annotations and no output schema, the description covers the core mechanics, cost, and failure mode but leaves return values and several parameter meanings unexplained. It is adequate for a rough call attempt but not complete for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 explain seven parameters and only partially does so. It conceptually maps the schedule, cashflow, and payout inputs and explains annual_rate usage, but says nothing about currency, opening_balance, minimum_balance, direction, labels, or the per-item date format, leaving most parameter meaning to the bare 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 states a specific verb and resource: stress-test a caller-supplied loan schedule, cashflow stream, and payout list. That is clear enough to distinguish it from a covenant or waterfall calculator, though it does not explicitly name or contrast with any sibling tool.

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?

The description implies the scenario via shift rules and the 'not a credit decision' caveat, and it notes that unpaid calls return 402. It does not explicitly say when to choose this over the sibling covenant, dilution, or waterfall tools, so routing guidance is only implied.

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