Skip to main content
Glama

audit_website_and_markdown

Safely audit public URLs for HTTP security headers and TLS configuration issues, or extract their web pages as clean Markdown.

Instructions

SSRF-safe HTTP security header/TLS audit or clean Markdown page extractor for public URLs.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http/https URL
modeNoaudit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

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 burden and only discloses that the tool is SSRF-safe and restricted to public URLs. It does not explain what an audit returns, how Markdown extraction behaves, whether the operation is read-only, how failures are handled, or whether rate limits or authentication apply.

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?

The definition is a single front-loaded sentence with no filler, and the SSRF-safety constraint appears before the functional description. It is compact but slightly compressed by covering two distinct modes in one phrase.

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?

For a network-facing tool with two modes, no annotations, no output schema, and only partial parameter documentation, the description is too thin. It leaves unclear what each mode returns, how mode selection affects behavior, and what limitations apply beyond public-URL enforcement.

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 50%: the URL parameter is documented in the schema, and the description adds the important constraint that URLs must be public. The mode enum is only named in the schema, while the description supplies meaningful semantics by explaining that one mode audits headers/TLS and the other extracts clean Markdown.

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 names two concrete operations, an HTTP security header/TLS audit and a Markdown page extractor, plus the target resource (public URLs). It is distinguishable from the unrelated sibling tools, though combining two modes in one sentence makes the tool's primary purpose slightly less sharp.

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?

The description identifies two possible modes but gives no explicit guidance on when to choose audit versus markdown, no when-not-to-use conditions, and no alternatives. An agent can infer mode intent from the enum names, but the definition itself provides little routing guidance.

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