Skip to main content
Glama

Retry traffic amplification

bpj_system_retry_amplification
Read-onlyIdempotent

Estimate expected attempts per operation and final failure probability with independent attempts and a cap.

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": {
      "failure": "<failure>",
      "attempts": "<attempts>"
    },
    "name": "bpj_system_retry_amplification"
  }
}

Input Schema

NameRequiredDescriptionDefault
failureYes
attemptsYes

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 establish this as a pure, idempotent, non-destructive computation. The description adds the important modelling premise that attempts are independent and capped, which affects how the result should be trusted, but says nothing about the formula, units, or what the returned numbers represent (probability vs. count).

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 front-loaded sentence with no filler; the two outputs and the two modelling constraints are stated economically. Slightly more framing on inputs would not have hurt, but nothing is wasted.

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 small two-parameter calculator without an output schema, the description covers what it computes and the key assumption. It still falls short on how to interpret the returned values and when this tool is the right choice among many retry-related siblings.

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 coverage is 0% and only titles are present, so the description is the only place meaning is added. 'Independent attempts and a cap' hints that 'failure' is a per-attempt probability and 'attempts' is the cap, but it does not spell out that inputs are probabilities on 0-1 or that the cap bounds the retry loop.

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 verb 'Estimate' with the objects 'expected attempts per operation' and 'final failure probability' makes the computation concrete and distinguishes it from pure lookup tools. It does not, however, name or differentiate itself from near neighbours like bpj_billing_retry_recovery or bpj_system_backoff_timeline.

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?

The description gives no indication of when to reach for this calculator versus a sibling, nor any prerequisite context (e.g. that failure probabilities must be independent). The agent must infer the boundary entirely from the name and inputs.

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.