Skip to main content
Glama

net-web-media

cache_control_parse_and_build

Parse or build HTTP Cache-Control headers (max-age, s-maxage, stale-while-revalidate, immutable, private, no-store) with CDN vs browser TTL breakdown.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cache_control_parse_and_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
headerNo
presetNocdn-swr

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states the domain and mentions a TTL breakdown, but it does not clarify whether the operation is pure/read-only, whether any network call occurs, how errors are surfaced, or what the output structure looks like.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no filler. It is efficient, though the brevity contributes to the missing parameter and mode guidance rather than being a model of completeness.

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

Completeness2/5

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

For a tool with three undocumented parameters, a mode switch between parsing and building, and no output schema, the description is substantially incomplete. It identifies the subject matter well but leaves the agent unable to determine how to invoke the correct mode with the correct parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain any of the three parameters. It does not say that text is input for parsing, header is input for building, or what the preset enum values mean, so it adds no usable meaning beyond the bare schema.

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 gives a specific verb pair (parse/build) and resource (HTTP Cache-Control headers), and it names concrete directives and a CDN vs browser TTL breakdown. It is clearer than a tautology and distinguishable from siblings like http_headers_security_audit, though it does not explain the parse-vs-build mode choice.

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

Usage Guidelines2/5

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

The description says what the tool handles but gives no explicit guidance on when to use it versus alternatives, nor when to use parsing versus building. It does not explain whether the text, header, or preset parameters select those modes or when each is appropriate.

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.

Resources