Skip to main content
Glama

Request error budget burn rate

bpj_system_error_budget_burn
Read-onlyIdempotent

Divide observed request error fraction by the allowed fraction to obtain the burn multiple.

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": {
      "requests": "<requests>",
      "errors": "<errors>",
      "target": "<target>"
    },
    "name": "bpj_system_error_budget_burn"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorsYes
targetYes
requestsYes

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 a read-only, idempotent, closed-world calculation, so the safety profile is covered. The description adds that the operation is a division producing a burn multiple, but it omits edge behavior such as output type, rounding, and how a target success fraction becomes an allowed error fraction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single front-loaded sentence stating the calculation. No filler; every phrase contributes to the formula.

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 simple read-only calculator the description gives enough to understand the intended computation, and annotations cover the safety profile. However, with no parameter descriptions and an ambiguity between target success fraction and allowed error fraction, it is only minimally sufficient for correct 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?

With 0% schema description coverage, the description must define the three inputs, but it only indirectly refers to them as 'observed request error fraction' and 'allowed fraction'. In particular, the schema calls target a 'Target success fraction' while the description calls the divisor an 'allowed fraction,' leaving whether that is an allowed error or success fraction ambiguous.

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 operation (divide observed error fraction by allowed fraction) and the result (burn multiple). It is clear what the tool computes, but it does not distinguish this from related system/reliability calculators among the siblings.

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?

No explicit when-to-use, when-not-to-use, or alternative tools are named. The formula implies an error-budget context, but the agent must infer the scenario and cannot tell why to choose this over sibling reliability calculators.

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.