Burs-IA Utils

Plan de reintentos con espera

backoff-schedule

Read-onlyIdempotent

Calcula los tiempos de espera entre reintentos (exponencial, lineal o constante) con tope y jitter opcional. Cuándo: un flujo de agente necesita un resultado exacto y repetible para un paso auxiliar (tokens, costos, reintentos, fragmentos, ranking, limpieza de JSON). No para: interpretar Retry-After (retry-after-parse). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Computes retry delays for exponential, linear or constant backoff with a cap and optional jitter (full, equal or decorrelated; seeded for reproducibility), and the cumulative wait. When: an agent loop needs an exact, repeatable result for a bookkeeping step (tokens, costs, retries, chunking, ranking, JSON clean-up). Not for: parsing an HTTP Retry-After value (retry-after-parse). [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`seed`	No	Seed for jitter (reproducible) (string; optional; up to 100 chars).
`factor`	No	Multiplier for exponential (number; optional; default 2; min 1; max 10).
`jitter`	No	Jitter (optional; one of: none, full, equal, decorrelated; default "none").	none
`max_ms`	No	Cap per delay ms (number; optional; default 30000; min 0; max 86400000).
`base_ms`	No	Base delay ms (number; optional; default 500; min 0; max 3600000).
`retries`	No	Number of retries (integer; optional; default 5; min 1; max 100).
`strategy`	No	Strategy (optional; one of: exponential, linear, constant; default "exponential").	exponential

Output Schema

Name	Required	Description	Default
`total_ms`	No
`delays_ms`	No
`cumulative_ms`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Computes retry delays for exponential, linear or constant backoff with a cap and optional jitter (full, equal or decorrelated; seeded for reproducibility), and the cumulative wait. When: an agent loop needs an exact, repeatable result for a bookkeeping step (tokens, costs, retries, chunking, ranking, JSON clean-up). Not for: parsing an HTTP Retry-After value (retry-after-parse). Side effects: none (read-only, no network access, no stored state). Deterministic: the same input gives the same output. Limits: JSON input up to 64 KB, 1 s per call, result up to 1 MB."

First observedNov 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare read-only, non-open-world, idempotent, and non-destructive behavior. The description adds important context beyond annotations: no network, no stored state, deterministic output, and concrete limits of 64 KB input, 1 second per call, and 1 MB result.

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

Conciseness3/5

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

The content is front-loaded and every major section is useful, but the description is duplicated in Spanish and English and ends with an odd pointer to inputSchema.description. The bilingual repetition makes it longer than necessary for a tool whose schema already carries detailed parameter documentation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, complete parameter descriptions, and rich annotations; the description still supplies the remaining context an agent needs: purpose, alternatives, determinism, side effects, and execution limits. Nothing essential for correct invocation is missing.

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?

The input schema has 100% description coverage for all seven parameters, including defaults, ranges, and enums. The description usefully names the backoff strategies and jitter modes, but it mostly restates schema-level semantics rather than adding parameter-specific detail beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: computes retry delays for exponential, linear, or constant backoff, with cap and optional jitter, plus cumulative wait. It explicitly distinguishes itself from the sibling retry-after-parse, so an agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

It provides explicit when-to-use guidance for an agent loop needing exact, repeatable bookkeeping results. It also names the specific alternative, retry-after-parse, and states when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Burs-IA Utils tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?