Skip to main content
Glama

Audit security headers

bursia_security_headers
Read-onlyIdempotent

Audit HTTP security headers of a public HTTPS page (HSTS, CSP, X-Content-Type-Options, frame protection, Referrer-Policy, Permissions-Policy). Read-only GET, no redirects followed. Free.

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

Input Schema

NameRequiredDescriptionDefault
urlYesDomain or https URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral facts: it performs a single GET with no redirect following (so a redirecting URL will not yield the destination's headers) and it is free — both material to correct invocation.

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 short sentences, front-loaded with the action and the audited header set, followed by the operational caveats. No filler or restatement of the title.

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 one-parameter read-only audit with no output schema, the description covers scope, transport behavior, and cost. The only gap is what the result looks like qualitatively (per-header pass/fail vs. raw values), which is not required given no output schema but would help agents interpret results.

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 coverage ('Domain or https URL'), so the schema does the documentation work. The description's phrase 'of a public HTTPS page' adds a validity constraint (public, HTTPS) that is not in the schema, but adds no further format or normalization detail.

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 ('HTTP security headers of a public HTTPS page') and enumerates the exact headers inspected (HSTS, CSP, X-Content-Type-Options, frame protection, Referrer-Policy, Permissions-Policy). This clearly separates it from adjacent siblings such as bursia_tls_certificate, bursia_dns_records, or bursia_check_agent_card, which target 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?

The 'public HTTPS page' constraint and 'no redirects followed' note imply when the tool applies, but no alternative tool is named and no explicit when-not guidance is given (e.g., what to use for cert inspection or for private/non-HTTPS targets). Usage is inferable rather than stated.

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