Skip to main content
Glama

net-web-media

http_headers_security_audit

Audit raw HTTP response headers for HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and server fingerprint leakage.

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": "http_headers_security_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoRaw HTTP headers lines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the specific security checks it performs, which is genuine behavioral context beyond the name, but it omits how findings are reported (issues only vs. all headers, severity levels) and whether any network access occurs. That leaves meaningful behavioral gaps for an audit tool.

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?

One sentence, front-loaded with the verb and resource, with the check list following. Every element earns its place and there is no filler.

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?

The tool is simple (one optional string parameter), and the check coverage is spelled out. With no output schema and no annotations, however, the description should say something about what the audit returns, since that is the only place an agent could learn 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 parameter with 100% schema description coverage ('Raw HTTP headers lines'), so the schema already documents it. The description restates the same idea as 'raw HTTP response headers' without adding formatting details (e.g., whether status line or folded headers are expected), so 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?

States a specific verb ('Audit') and resource ('raw HTTP response headers'), then enumerates the exact checks performed (HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, server fingerprint leakage). This clearly distinguishes it from sibling audits such as html_accessibility_audit and har_performance_analyze.

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 phrase 'raw HTTP response headers' implies the input must be captured header text rather than a URL, which is a useful usage cue. However, there is no explicit statement of when to use this versus alternatives, no prerequisites, and no note on what a caller should expect (e.g., that no network fetch occurs).

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