Skip to main content
Glama
offsec-mcp

offsec-mcp

by nadirzhon

Security Headers

security_headers

Audit an authorized site's HTTP security headers and assign an A–F grade to identify missing protections.

Instructions

Audit a site's HTTP security headers and grade them A–F. [active — needs scope]

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
urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two meaningful traits: the scan is 'active' (it sends requests to the target) and it requires scope authorization. It says nothing about rate limits, failure modes, or whether the target must be owned, so a mutation-adjacent active tool remains partially opaque.

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?

Two compact fragments, front-loaded with the purpose before the bracketed qualifier; nothing is wasted. The bracket notation is terse to the point of ambiguity, which keeps it just under top marks.

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?

An output schema exists, so return values needn't be explained, and the active/scope caveat covers the main behavioral risk. However, with zero annotation coverage and zero parameter documentation, the definition leaves an agent guessing about URL format and what 'needs scope' concretely requires.

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

Parameters2/5

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

Schema coverage is 0% and the single required 'url' parameter is undocumented. 'A site's' only loosely implies the parameter is a site URL, with no guidance on whether a scheme, path, or bare hostname is expected, so the description does not compensate for the schema gap.

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 and resource ('Audit a site's HTTP security headers') plus the output shape ('grade them A–F'), which is enough to separate it from siblings like http_probe or port_scan. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiated.

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 '[active — needs scope]' tag implies this is an active scan that requires an in-scope target, which is a useful usage condition, but it is cryptic and never states when to prefer this over http_probe or what happens if scope is missing. Usage is implied rather than spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.