Burs-IA Utils

Explicar código de estado HTTP

http-status

Read-onlyIdempotent

Explica un código de estado HTTP: frase estándar (inglés y español), clase, significado y si conviene reintentar. Cuándo: hay que leer, construir o revisar con exactitud una URL, una cabecera HTTP, un token, una versión, un rango de IP, un documento HTML o Markdown o un archivo para agentes. No para: convertir un bloque de encabezados HTTP crudos en un objeto con nombres en minúscula (http-headers-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: Explains an HTTP status code: standard reason phrase (English and Spanish), class, short meaning, and whether a client should typically retry it. When: a URL, HTTP header, token, version string, IP range, HTML or Markdown document or agent-readiness file has to be parsed, built or checked exactly. [EN completo / full EN: inputSchema.description]

Input Schema

Name	Required	Description	Default
`code`	Yes	HTTP status code (integer; required; min 100; max 599).

Output Schema

Name	Required	Description	Default
`code`	No
`class`	No
`known`	No
`reason`	No
`meaning`	No
`reason_es`	No
`retryable`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / code / examples
```
Added value: +[
+  429
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Explains an HTTP status code: standard reason phrase (English and Spanish), class, short meaning, and whether a client should typically retry it. When: a URL, HTTP header, token, version string, IP range, HTML or Markdown document or agent-readiness file has to be parsed, built or checked exactly. Not for: parsing a raw HTTP header block (http-headers-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.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint=false, so the safety profile is pre-established. The description still adds real value beyond them: no network access, no stored state, determinism guarantee, and explicit limits (64 KB input, 1 s per call, 1 MB result). It does not describe the shape of the returned explanation, though the output schema covers that.

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 Spanish paragraph is front-loaded and structured (Cuándo / No para / Efectos / Determinista / Límites), which is good. But the trailing English restatement plus the truncated placeholder '[EN completo / full EN: inputSchema.description]' is wasted, confusing text that adds no information and inflates the definition.

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

Completeness4/5

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

For a one-parameter, read-only lookup with full schema coverage and an output schema, the description supplies everything an agent needs to call it correctly, including limits and determinism. The only shortfall is the vague positive trigger condition, which is a minor gap given how narrow the tool is.

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 100% and the single parameter already documents type, required status, minimum 100 and maximum 599 plus an example. The description adds no additional semantics beyond the valid range, so the baseline 3 for a fully documented schema is appropriate.

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?

States a specific verb+resource ('Explica un código de estado HTTP') and enumerates the exact output fields: standard reason phrase in English and Spanish, class, meaning, and retry guidance. This is distinguishable from every sibling, including the nearest one (http-headers-parse).

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

Usage Guidelines4/5

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

It explicitly excludes the nearest alternative — 'No para: convertir un bloque de encabezados HTTP crudos... (http-headers-parse)' — which is genuinely useful routing. However, the positive 'Cuándo' clause is generic boilerplate about parsing URLs, tokens, IP ranges and HTML/Markdown files, and never describes the actual condition for looking up a status code. Clear context, but the when-clause is misaligned with the 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?