Skip to main content
Glama

BRAINIAC Financial Schedule & Credit Calculations

Calculate covenant headroom

fintech_covenant-headroom-calculate

Compute headroom for caller-supplied financial covenants against metric values and thresholds. Returns the exact threshold, headroom formula, and breach status. No credit bureau is contacted. Price $0.04 USDC. POST /api/v1/fintech/covenant-headroom-calculate. 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": {
      "metrics": "<metrics>",
      "covenants": "<covenants>"
    },
    "name": "fintech_covenant-headroom-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
metricsYes
currencyNo
covenantsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it does disclose useful traits: no credit bureau contact, a $0.04 USDC price, and that unpaid calls return 402 without running. However, it says nothing about how metric_id references that don't resolve are handled, validation failure behavior, or whether the operation is purely computational and side-effect free.

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: purpose first, then return contents, then side-effect/billing, then failure mode. Every sentence carries information; the endpoint path is the only near-redundant element given the tool name.

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 3-parameter computational tool with no output schema and no annotations, the description reasonably covers returns, billing, and failure behavior. The significant remaining gap is the structure and linkage semantics of the two nested array parameters, which have 0% schema documentation.

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% across three parameters, two of which are nested arrays of objects with required fields (metrics id/name/value, covenants id/metric_id/operator/threshold). The description mentions 'metric values and thresholds' but does not explain how covenants link to metrics by metric_id or what the operator enum means.

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: 'Compute headroom for caller-supplied financial covenants against metric values and thresholds.' The subject matter (covenant headroom) is clearly distinct from the sibling tools' domains (dilution, waterfall, schedule risk), though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus alternatives, no prerequisites, and no exclusions. 'Caller-supplied' implicitly signals that the caller must already hold the metrics and covenants, but the agent must infer that this tool performs no data retrieval.

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