Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

Security headers check

security_headers
Read-onlyIdempotent

Use when the user asks which security headers a live website sends or if it forces HTTPS. Returns the redirects from http:// and https:// and HSTS, CSP, frame protection, Referrer-Policy and cookie flags. Ex: 'Which security headers does example.com miss?'. Free trial without an API key: a few calls a day.

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": {
      "domain": "<domain>"
    },
    "name": "security_headers"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark it read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds useful behavior beyond that: it fetches live HTTP/HTTPS responses, returns redirect behavior and specific header categories, and discloses a free-trial rate limit of 'a few calls a day' without an API key.

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?

The description is front-loaded with the primary use case, then lists the returned data, then gives a concrete example and access note. Every sentence contributes without repetition or marketing bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 adequately characterizes what comes back: redirects from both schemes and the main security header categories. It also covers selection context and access constraints, leaving no critical gap for invoking the tool correctly.

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 only one parameter, domain, and schema description coverage is 100%, so the schema already explains it. The description supplies an example domain only through the usage example, adding little parameter-specific meaning beyond the schema baseline.

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?

The description states a specific verb and resource: checks the security headers a live website sends and whether it forces HTTPS. It also enumerates the returned artifacts (redirects, HSTS, CSP, frame protection, Referrer-Policy, cookie flags), which clearly separates it from DNS/mail-focused siblings such as dmarc, spf, or mx.

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?

It gives a clear trigger: 'Use when the user asks which security headers a live website sends or if it forces HTTPS.' This is sufficient for an agent to select it over DNS record or mail configuration tools. It does not explicitly name alternatives or exclusions, but the live-website scope is a strong implicit boundary.

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.