Skip to main content
Glama

check_headers

Read-only

Inspect security headers for up to 5 URLs: HSTS, CSP, clickjacking protection, cookie flags (names only, never values), Server/X-Powered-By disclosure, HTTPS redirect, a simple letter grade and plain recommendations. HEAD is used first, with a small GET if needed. No TLS certificate handshake. Price: 0.01 USDC per call (x402, Base).

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": {
      "urls": "<urls>"
    },
    "name": "check_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesURLs or domains to inspect

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

With annotations only covering readOnlyHint and openWorldHint, the description adds substantial operational detail the annotations cannot: privacy behavior (cookie names only, never values), request strategy (HEAD then minimal GET), a deliberate non-goal (no TLS handshake), and the output shape (letter grade plus plain recommendations). Pricing at 0.01 USDC per call via x402 on Base is genuinely valuable pre-invocation context; only a note on rate limits or failure behavior for unreachable URLs is missing.

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?

Front-loaded with the core action, then two short sentences for execution strategy and cost, with no filler. The clause list in the first sentence is dense but every item is informative payload rather than padding.

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?

No output schema exists, yet the description still tells the agent what comes back (letter grade, plain recommendations, per-check findings), which is what makes it callable. Coverage is complete for a single-parameter read tool; only edge-case handling for invalid or unreachable URLs is unaddressed.

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

Parameters4/5

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

One parameter at 100% schema coverage already documents that it accepts URLs or domains, and the description reinforces the maxItems=5 bound as 'up to 5 URLs.' That restatement is mildly useful but adds no new syntax or normalization guidance (e.g., whether bare domains are auto-prefixed with https), so it sits at the high-coverage baseline.

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?

Names a specific verb (inspect) and resource (security headers) and enumerates exactly what is checked: HSTS, CSP, clickjacking, cookie flags, Server/X-Powered-By, HTTPS redirect, grade, recommendations. Scope is bounded (up to 5 URLs), so an agent can tell precisely what this tool returns 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 Guidelines3/5

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

Usage context is implied by the content (auditing header hygiene for a small set of URLs), and it states an execution strategy (HEAD first, small GET if needed). However, it never says when to prefer this over sibling tools such as verify_links or site_policies, and gives no exclusions or prerequisites for choosing it.

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