Skip to main content
Glama

Interpret Retry-After

bpj_interpret_retry_after
Read-onlyIdempotent

Convert a Retry-After delta or IMF-fixdate header into a wait duration and UTC timestamp.

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": {
      "header": "<header>",
      "observed": "<observed>"
    },
    "name": "bpj_interpret_retry_after"
  }
}

Input Schema

NameRequiredDescriptionDefault
headerYes
observedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this as a pure, idempotent, non-destructive, closed-world read, so the safety profile is fully covered. The description adds that both header formats are handled and that two values come back, but says nothing about invalid/unparseable headers, negative or zero deltas, or how the observed time is consumed — the behavior most likely to surprise a caller.

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?

A single sentence, front-loaded with the verb and resource, with no filler or restated title. Nothing could be removed without losing information.

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 two-parameter pure function with no output schema and rich annotations, the description covers purpose and the header's two forms but leaves the meaning of 'observed', the shape of the returned duration (seconds? milliseconds?), and invalid-input behavior unaddressed. Adequate but clearly short of complete.

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% (only field titles), so the description is expected to compensate. It does clarify the 'header' parameter by naming the two accepted formats, but adds nothing about 'observed' — notably that the ISO observation time is what makes delta-to-UTC-timestamp conversion possible. One parameter gains meaning, the other remains opaque.

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 ('Convert') and a specific resource ('Retry-After ... header') and enumerates both accepted input encodings (delta-seconds or IMF-fixdate) plus both outputs (wait duration, UTC timestamp). That is enough for an agent to tell this apart from generic time helpers like bpj_convert_timestamp, though it never states the distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the mention of 'Retry-After header' suggests parsing HTTP 429/503 responses, but the description never says when to call this versus a timestamp converter, nor any preconditions (e.g., header must originate from a live response with a known observation time). No exclusions or alternatives are given.

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.