Skip to main content
Glama

Interest Service Headroom

bpj_interest_service_headroom
Read-onlyIdempotent

Calculate interest coverage and remaining earnings after interest from current-period EBIT.

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": {
      "ebit": "<ebit>",
      "interest": "<interest>"
    },
    "name": "bpj_interest_service_headroom"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebitYes
interestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds the useful scoping detail that EBIT should be current-period, but it omits a real behavioral hazard: interest has a schema minimum of 0, so an interest expense of zero makes the coverage ratio undefined, and no warning or stated behavior is given for that case.

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 that front-loads the verb and the two outputs with no filler. It could usefully spend one more short clause on the zero-interest edge case rather than staying this terse.

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?

The tool is simple (two numeric inputs, no output schema), so the burden is moderate, and the description does name both returned quantities. It falls short on the interest-equals-zero division case and on any indication of output form (ratio vs. percentage, currency of remaining earnings).

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 meaning, and it only partly does. It clarifies that ebit is current-period EBIT, but it does not state whether interest is a period figure or an annualized rate, nor clarify units, despite the parameters' names and titles being mostly self-explanatory.

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 specific verb (calculate) and two specific outputs: interest coverage and remaining earnings after interest, plus the input basis (current-period EBIT). It is unambiguous what the tool computes, but it offers no differentiation from similar finance siblings such as bpj_debt_service_covenant or bpj_project_commitment_headroom.

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 use this tool, when not to, or which alternative to pick for related covenant/headroom questions that appear in the sibling list. The agent must infer the usage context entirely from the tool name.

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.