Skip to main content
Glama

Security Headers + TLS Audit

audit_secheaders_lite

Read-onlyIdempotent

FREE lite security headers + TLS audit of a website URL. Runs the same 11 checks as audit_secheaders but returns top-line results only: 0-100 score, A-F grade, exposure-risk level, check counts, and the titles of the top gaps — detail is capped (no per-check evidence, no site block, no detailed fixes). Use this to triage whether a site needs the full audit_secheaders report, or call audit_secheaders directly for the complete evidence-backed scan.

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

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite URL to audit (https preferred), e.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive, so the safety profile is covered; the description then adds the substantive behavioral facts an agent could not otherwise know — what the response contains (0-100 score, A-F grade, risk level, check counts, top gap titles) and precisely what is truncated (no per-check evidence, no site block, no detailed fixes). That limitation disclosure is the key value-add beyond annotations.

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-loads the core purpose and the 'same checks, reduced output' framing before the routing advice. Dense but nearly every clause carries signal; the 'FREE' lead and the parenthetical list of omissions are slightly promo-flavored but still informative rather than filler.

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?

No output schema exists, and the description compensates by enumerating the returned fields and the deliberate omissions, which is exactly what is needed to interpret results. Combined with the single fully documented parameter, an agent has everything required to call it and act on the response.

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 description coverage, so the schema already explains the url argument and the https preference. The description adds no format, validation, or edge-case detail on the URL beyond what the schema supplies, so the baseline of 3 applies.

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 ('security headers + TLS audit of a website URL') and immediately scopes it against the sibling: same 11 checks as audit_secheaders but top-line results only. An agent can distinguish this from the full audit without opening either schema.

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

Usage Guidelines5/5

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

Gives explicit routing guidance in both directions: use this to triage whether a site needs the full audit_secheaders report, or call audit_secheaders directly for the complete evidence-backed scan. The selection condition (triage vs. full evidence) is stated, not inferred.

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.