Skip to main content
Glama

Debt Service Covenant Check

bpj_debt_service_covenant
Read-onlyIdempotent

Compare cash available for debt service with a minimum coverage covenant and quantify the cash headroom.

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": {
      "cashFlow": "<cashFlow>",
      "due": "<due>",
      "minimum": "<minimum>"
    },
    "name": "bpj_debt_service_covenant"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueYes
minimumYes
cashFlowYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered externally. The description adds only the fact that a headroom figure is produced, without saying whether results are ratios, currency amounts, signed, or what happens at exactly the covenant threshold; with annotations doing the heavy lifting, this is adequate but thin.

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?

A single well-formed sentence with the comparison front-loaded and no filler. It is efficient, though its brevity comes at the cost of the clarifications noted elsewhere.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a derived-value calculator with three required numeric inputs, 0% schema coverage, and no output schema, so the description must define both the formula and the return shape. It does neither, leaving the agent unable to predict whether the output is a ratio, a boolean pass/fail, or a signed headroom amount.

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 carry the parameter burden, and it only loosely restates the schema titles ("cash available for debt service" for cashFlow, "minimum coverage covenant" for minimum) while never mentioning 'due' explicitly. Critically, the arithmetic relationship is unstated — it does not say whether the covenant test is cashFlow/due against minimum or a currency shortfall against due — which is the main semantic the agent needs.

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 names a concrete verb ("compare") and the two quantities being compared (cash available for debt service vs. a minimum coverage covenant), plus the derived result (cash headroom). It does not differentiate itself from related computation siblings such as bpj_interest_service_headroom, so it stops short of a 5.

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 guidance on when to call this versus alternatives, no prerequisite conditions (e.g., inputs must be positive or in the same currency/period), and no exclusions. The single sentence describes what the tool does, leaving the agent to infer usage context entirely.

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.