Skip to main content
Glama

Security headers

security_headers
Read-onlyIdempotent

Grade HTTP response security headers (0-100): HSTS, CSP, X-Frame-Options, nosniff, Referrer-Policy, Permissions-Policy, cookies. $0.002 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnly/idempotent/openWorld; the description adds the crucial non-obvious behavior that the tool is metered ('$0.002 per call') and settles payment inline over x402 with named chains. The one nuance unaddressed is that a 'purchase' inside a readOnly-annotated call is a billing side effect, which the annotations do not surface — but the description at least makes it visible rather than contradicting it.

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?

Three compact sentences: capability, price, then protocol. Capability and coverage are front-loaded, and no sentence is filler despite the density of chain and pricing detail.

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?

With no output schema, the description still signals the return shape ('Grade ... (0-100)' over a named header list), and it fully explains the payment prerequisite, which is the main failure mode for callers. It stops short of describing per-header breakdown or error behavior when a URL 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 coverage is 100%, so baseline is 3, but the description adds real meaning the schema lacks: the two-phase protocol of omitting `payment` first to obtain terms and supplying a wallet-signed payload second to complete the call. That sequencing is actionable information not derivable from the property descriptions alone.

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 and resource ('Grade HTTP response security headers (0-100)') and enumerates exactly which headers are assessed. An agent can distinguish it from siblings like tls_cert or robots_check without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit invocation procedure: 'Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`.' It does not, however, say when to reach for this versus tls_cert or other security-adjacent siblings, so differentiation is left to the name and header list.

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