Skip to main content
Glama

http_audit

Audit HTTP services by checking title, headers, server banner, allowed methods, and robots.txt on a target, optionally across specified ports.

Instructions

Check HTTP title, headers, server banner, allowed methods, and robots.txt on a target.

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": {
      "target": "<target>"
    },
    "name": "http_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
portsNo80,443
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, and it offers little: it does not say whether live requests are sent to the target (detectable/loggable), how failures or unreachable ports are handled, or whether the operation is safe/read-only. It only enumerates what is collected.

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?

A single front-loaded sentence with no filler; every listed item is a real output of the check. It is short to a fault, but nothing is wasted.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but with zero annotation and zero schema-description coverage the definition should still clarify the undocumented ports parameter and request semantics. Those gaps leave an agent guessing about scope and side effects.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, yet it says nothing about the 'ports' parameter (default '80,443') or the expected 'target' format (hostname, URL, CIDR?). Only the vague phrase 'on a target' appears.

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 concrete verb ('Check') plus an explicit inventory of what is retrieved: title, headers, server banner, allowed methods, and robots.txt. That distinguishes it from siblings like ssl_audit or dns_audit by content, though it never names or contrasts them.

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?

No guidance on when to pick this over http-related alternatives (e.g., ssl_audit, quick_scan) or when it is unnecessary. No prerequisites such as reachability, scheme (http vs https), or authorization are stated.

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