Skip to main content
Glama

DomainVet

Grade a site's HTTP security headers

security_headers
Read-onlyIdempotent

Fetch a URL and grade its HTTP security headers A-F: HSTS (with max-age), Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/CORP. Also flags version-leaking headers (Server, X-Powered-By) and returns all response headers and the redirect chain.

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
urlYesSite URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the safety profile is covered. The description still adds useful behavior beyond them: it discloses that the call performs a live network fetch, that it follows and reports a redirect chain, and that it flags version-leaking headers like Server and X-Powered-By. Missing only operational detail such as timeouts or failure behavior on unreachable hosts.

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

Conciseness5/5

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

Two sentences, front-loaded with the core action and grade scale, followed by the enumerated checks and the return payload. Every clause contributes new information with no filler.

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

Completeness5/5

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

No output schema exists, so the description must carry return-value disclosure — and it does, naming the A-F grade, the graded headers, the version-leak flags, all raw response headers, and the redirect chain. For a one-parameter read tool with annotations covering safety, nothing material is missing.

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 'url' parameter at 100% schema coverage, and the description says only 'Fetch a URL', adding no format constraints (scheme requirements, trailing paths) beyond the schema. With the schema doing the documentation work, the baseline of 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?

The description pairs a specific verb and resource — 'Fetch a URL and grade its HTTP security headers A-F' — and then enumerates exactly which headers are graded (HSTS, CSP, X-Frame-Options, and the rest). This is clearly distinct from siblings like ssl_certs or dns_lookup, which operate on different artifacts.

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 content: the tool is for auditing a site's HTTP response headers. There is no explicit statement of when to prefer it over a sibling (for example, ssl_certs for TLS configuration) and no stated exclusions or prerequisites such as whether the URL must be reachable over HTTPS.

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