Skip to main content
Glama

AutoPay

security_scan_headers

Security headers check (passive only): HTTPS redirect, HSTS, CSP, X-Frame-Options/frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy; score + grade. $0.003; synchronous, charged only on success. Pay with X-PAYMENT (x402 USDC on Base) or a prepaid API key.

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

Input Schema

NameRequiredDescriptionDefault
urlNoSite URL, e.g. https://example.com
domainNoAlternative to url: bare domain, e.g. example.com

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?

With no annotations, the description carries the full burden and does substantial work: it discloses passive-only behavior, synchronous execution, a fixed price ($0.003), that charging occurs only on success, and the two accepted payment paths (X-PAYMENT x402 USDC on Base or prepaid API key). What it omits is failure/error behavior beyond non-billing, any rate limits, and whether results are deterministic or cached.

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 purpose and scope, then a compact second block on cost, execution mode, and payment; no filler sentences. It is dense to the point of being semicolon-crammed, and the payment-mechanics clause sits in the tool description rather than structured data, which costs a point on polish but not on usefulness.

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?

For a two-parameter passive scanner with no annotations and no output schema, the description supplies what the agent actually needs to decide and to pay correctly: scope, cost, billing condition, sync behavior, and auth method. Gaps are minor — no explicit statement of the response structure beyond 'score + grade' and no note on what happens when the target is unreachable.

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?

Schema description coverage is 100%, so the two parameters are already self-documenting, and the description adds no parameter detail of its own — the '0 params = baseline 4' rule does not apply but the schema-coverage rule gives a baseline of 3. It edges slightly above baseline because the scoping language ('headers check ... on a site') reinforces that url/domain identify a single target, though it never clarifies precedence if both are supplied.

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 (check) and resource (security headers) and enumerates exactly which headers are inspected (HTTPS redirect, HSTS, CSP, X-Frame-Options/frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy), plus the output shape (score + grade). Against siblings like security_scan_tls, security_scan_dns, or security_scan_exposure, the enumerated scope makes the boundary obvious without opening any 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?

The parenthetical 'passive only' implies this is the non-intrusive option versus active scans, and the header list implies use when auditing browser-facing security configuration. But there is no explicit when-to-use rule, no named alternative (e.g. 'for TLS configuration use security_scan_tls'), and no exclusion such as 'does not fetch page content'.

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