Burs-IA Utils

Leer Cache-Control

cache-control-parse

Read-onlyIdempotent

Analiza Cache-Control en directivas y resume si es almacenable en cachés compartidas o privadas. 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: Parses a Cache-Control header into directives (max-age, s-maxage, no-store, private, immutable, stale-while-revalidate…) and summarizes cacheability by shared and private caches. 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	Cache-Control value (string; required; up to 4096 chars).

Output Schema

Name	Required	Description	Default
`directives`	No
`ttl_seconds`	No
`must_revalidate`	No
`cacheable_shared`	No
`cacheable_private`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026
- addedInput schema / properties / header / examples
```
Added value: +[
+  "public, max-age=3600, stale-while-revalidate=60"
+]
```

Changed1 schema field changedNov 1, 2026

addedInput schema / description

Added value: +"EN: Parses a Cache-Control header into directives (max-age, s-maxage, no-store, private, immutable, stale-while-revalidate…) and summarizes cacheability by shared and private caches. 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 declare readOnly, idempotent, non-destructive and no open-world access, and the description largely echoes that. It does add value beyond annotations: determinism ('same input, same output') and concrete limits (64 KB input, 1 s per call, 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?

Purpose is front-loaded and clear, but the 'Cuándo' enumeration (URL, token, version, IP range, HTML, Markdown, agent-readiness file) is irrelevant boilerplate that adds noise rather than helping select this tool. It sits alongside useful side-effect and limit statements.

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?

A single-param read-only tool with an output schema (so return values needn't be explained), determinism, no-side-effect and limit disclosures. Nothing essential for correct invocation is missing; only the noisy 'Cuándo' clause detracts.

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?

Only one parameter with 100% schema description coverage, so the schema already documents the header value, format and length. The description adds no syntax or format detail beyond what the schema states, 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?

States a specific verb and resource: parses a Cache-Control header into directives and summarizes shared/private cacheability. It names the exact sibling it replaces (http-headers-parse), so an agent can distinguish it 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 Guidelines4/5

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

Provides an explicit 'No para' exclusion routing the agent to http-headers-parse for raw header blocks, which is genuinely useful. However the 'Cuándo' clause is boilerplate listing URLs, tokens, IP ranges, HTML/Markdown docs that has little to do with Cache-Control parsing, diluting the guidance.

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?