Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_compliance_security_headers_audit

Fetch a URL and grade its HTTP security headers to identify missing protections and support compliance checks.

Instructions

[Compliance & Trust] Fetch a URL and grade its HTTP security headers Measured p50 12 ms, p95 16 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://compliance.caelaralabs.com.

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

Input Schema

NameRequiredDescriptionDefault
urlYesURL or hostname to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/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. It usefully discloses that the call is proxied to https://compliance.caelaralabs.com and gives latency figures, but it says nothing about whether the target URL is actually fetched live, what happens on unreachable hosts or redirects, whether the call has side effects, or what the 'grade' looks like. For an unannotated network-fetching tool that is a substantial gap.

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?

Three short sentences, purpose front-loaded after the category tag, no filler prose. The latency benchmark and endpoint details are compact and arguably useful, though the dated benchmark parenthetical is the least load-bearing part given the missing output and error semantics.

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?

For a one-parameter tool this covers the essentials: what it does, where it calls, and how fast it is. But with no output schema and no annotations, the absence of any indication of the return shape (letter grade, per-header findings, pass/fail) leaves the agent guessing about what it will get back.

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 documented as 'URL or hostname to audit,' so the schema does the work. The description adds nothing beyond it — it does not clarify whether a scheme is required, whether paths are honored, or whether bare hostnames get a default scheme.

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?

The description gives a specific verb and resource: 'Fetch a URL and grade its HTTP security headers.' That is concrete enough to distinguish it from siblings such as the SPF/DMARC grader or the SSL cert inspector, though it never names a sibling or an alternative explicitly, so differentiation relies on the reader's own inference.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to a sibling tool for adjacent checks. The 'Compliance & Trust' tag hints at a category but does not tell an agent what scenario should select this tool over the SPF/DMARC grader or domain trust composite.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools