Skip to main content
Glama

Generate a capped backoff schedule

bpj_system_backoff_timeline
Read-onlyIdempotent

List deterministic exponential backoff waits before retries and their cumulative duration, applying 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": {
      "initial": "<initial>",
      "factor": "<factor>",
      "cap": "<cap>",
      "attempts": "<attempts>"
    },
    "name": "bpj_system_backoff_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
capYes
factorYes
initialYes
attemptsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the description's main added value is 'deterministic' (no jitter, reproducible output) and that cumulative duration is reported. It does not state the output shape, units, or whether the sum includes the final capped wait, so it only modestly extends the structured data.

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?

One dense sentence that front-loads the resource and outcome, with no filler or redundancy.

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?

Four required numeric parameters, no output schema, and 0% schema coverage put the full burden on the description, which omits the formula, the indexing convention, and the return structure. For a math-producing tool this leaves enough ambiguity to mis-specify inputs.

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%, so the description must carry parameter meaning, but it only implies 'cap' via 'applying a cap' and never explains how initial, factor, and attempts combine. Crucially it leaves the cap ambiguous—per-wait versus cumulative—and does not say whether attempt 1 waits 'initial' or whether a trailing wait is emitted.

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: 'List deterministic exponential backoff waits before retries and their cumulative duration, applying a cap.' The agent can tell this produces a schedule rather than analyzing retry behavior, though it does not explicitly distinguish itself from the nearby retry/amplification sibling.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative such as a retry-amplification or queue-drain tool. The agent must infer the use case from the verb alone.

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.