Skip to main content
Glama

Cache-Control header reader

bpj_cache_control_reader
Read-onlyIdempotent

Read explicit browser and shared freshness from Cache-Control and flag conflicting directives.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "header": "<header>"
    },
    "name": "bpj_cache_control_reader"
  }
}

Input Schema

NameRequiredDescriptionDefault
headerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/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 safety is covered. The description adds one genuine behavioral trait beyond them - it flags conflicting directives - but says nothing about how malformed or empty header values are handled or how conflicts are reported.

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?

One sentence with no filler, and the primary capability is front-loaded ahead of the secondary conflict-flagging behavior. The density of terminology costs a little immediate readability but nothing is wasted.

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

Completeness3/5

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

For a single-input, no-output-schema tool, the description roughly conveys the return content (freshness values plus conflict flags). It stops short of covering input format expectations or malformed-header behavior, which are the remaining gaps an agent would hit when calling it.

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?

There is a single required parameter 'header' with 0% schema description coverage, so the description must carry the load. Saying it reads Cache-Control implies the input is the header value, but it never clarifies whether a bare value ('max-age=60, s-maxage=30') or a full 'Cache-Control: ...' line is expected.

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?

States a specific verb (read) and resource (Cache-Control), plus what it extracts: explicit browser (max-age) and shared (s-maxage) freshness, and conflict flagging. That distinguishes it from unrelated siblings like bpj_robots_meta_reader, though the phrase 'explicit browser and shared freshness' is compressed jargon an agent must decode.

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

Usage Guidelines3/5

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

Usage is implied by the resource name - parse a Cache-Control value - but the description gives no explicit when-to-use or when-not-to-use guidance, and names no alternative for adjacent tasks such as validating cache behavior end-to-end. Adequate but inferential.

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.