Skip to main content
Glama

Caelara Labs Compliance & Trust

security_headers_audit

Fetch a URL and grade its HTTP security headers

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_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesURL or hostname to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: no mention of network access, redirect/follow behavior, rate limits, whether the call is side-effect free, or what the grade scale looks like. 'Fetch a URL' hints at an outbound request but nothing more.

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?

One short sentence with the action and result front-loaded and zero filler. Nothing is padded or repeated from the schema.

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

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one required param, no nesting, no output schema), so the definition is close to sufficient for invocation. However, with no output schema the description should say what a 'grade' consists of and which headers are checked, and it does not.

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?

Schema coverage is 100% and the single parameter is already documented as 'URL or hostname to audit'. The description adds no syntax, scheme, or hostname-vs-URL handling detail beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (fetch, grade) and a precise resource (HTTP security headers), which implicitly separates it from siblings like ssl_cert_inspector and spf_dmarc_grader that inspect different artifacts. It never explicitly names a sibling or contrast, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative, even though ssl_cert_inspector and spf_dmarc_grader sit adjacent in scope. The auditing intent is inferable from 'audit' in the schema and 'grade' in the description, but the agent must guess the 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.

Resources