Burs-IA Utils

Leer Content-Type

content-type-parse

Read-onlyIdempotent

Analiza Content-Type en tipo, subtipo, sufijo (+json) y parámetros (charset, boundary…). 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: analizar Content-Security-Policy en directivas y señala configuraciones riesgosas (csp-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: Parses a Content-Type / media type header into type, subtype, structured-syntax suffix (+json) and parameters (charset, boundary…), lowercasing names. 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
`header`	Yes	Content-Type value (string; required; up to 2048 chars).

Output Schema

Name	Required	Description	Default
`type`	No
`params`	No
`suffix`	No
`subtype`	No
`media_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / header / examples
```
Added value: +[
+  "Text/HTML; Charset=\"UTF-8\""
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Parses a Content-Type / media type header into type, subtype, structured-syntax suffix (+json) and parameters (charset, boundary…), lowercasing names. 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 Content-Security-Policy header into directives and source lists, and flagging risky settings (csp-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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new operational facts: no network access, no stored state, determinism, and hard limits (64 KB input, 1 s, 1 MB result), which the annotations do not express.

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 core sentence is front-loaded and precise, but the 'when' inventory of unrelated artifact types is filler that does not help this tool's caller, and the Spanish/English duplication pads 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 single-parameter, read-only parse tool with an output schema and rich annotations, the definition covers purpose, alternative, side effects and limits — an agent has everything needed to call it correctly. The only shortfall is the slightly confusing scope list.

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?

With one parameter and 100% schema description coverage, the schema already documents the required 'header' string with maxLength 2048 and an example. The description adds only the normalization behavior (lowercasing names), not parameter-level meaning beyond the schema, so baseline 3 applies.

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 precise verb and resource: parse a Content-Type/media type header into type, subtype, structured-syntax suffix and parameters. It also names the sibling it is not (csp-parse), so an agent can distinguish it from other header parsers without opening the schema.

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 gives an explicit 'Cuándo' clause plus a 'No para' exclusion pointing at csp-parse, which is exactly the routing information an agent needs. The when-list is partly boilerplate (URLs, tokens, versions, IP ranges are not Content-Type artifacts), which dilutes the guidance slightly.

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?