Skip to main content
Glama

security_headers

Read-only

Security headers check for a public URL: fetches it and reports HSTS, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/CORP/COEP and cookie flags, with a 0-100 score, grade and concrete fixes. Not charged if the site cannot be reached. — $0.001 USDC per call via x402 v2 (Base or Solana).

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": {
      "url": "<url>"
    },
    "name": "security_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL to check

Output Schema

NameRequiredDescriptionDefault
okYes
urlNo
fixesNo
gradeNo
httpsNo
scoreNo
statusNo
cookiesNo
headersNo
final_urlNo
redirectsNo
full_auditNo
info_leaksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the behavioral burden and does so well: it discloses that the tool performs an outbound fetch, that the call costs $0.001 USDC via x402 v2 on Base or Solana, and that unreachable sites are not charged. It stops short of covering timeout, redirect, or rate-limit behavior, so it falls short of a 5.

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?

Purpose is front-loaded in the first clause, followed by the header list, then billing and failure terms. The long header enumeration is dense but each item conveys real coverage scope; only the COOP/CORP/COEP cluster could be compressed.

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?

An output schema exists, so return values need not be spelled out, yet the description still names the score, grade, and fixes an agent will receive. Combined with cost and non-charge-on-failure terms, this covers most of what an agent needs; only edge-case fetch behavior is absent.

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 parameter with 100% schema description coverage ('Public http(s) URL to check'), so the schema already does the work and a 3 baseline applies. The description reinforces the public-URL restriction, which is meaningful since internal/private targets are out of scope, but adds no format or error semantics beyond that.

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 concrete verb and resource ('Security headers check for a public URL: fetches it and reports...') and then enumerates exactly which headers and outputs are covered. That enumeration cleanly separates it from siblings like read_url, page_links, and domain_intel without needing to name them.

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?

The 'public URL' constraint and the per-call pricing imply when this tool applies, but there is no explicit when-to-use vs. when-not guidance and no mention of alternatives (e.g. read_url for body content). The agent must infer the boundary between this and the sibling fetching tools.

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