Skip to main content
Glama

audit_website_and_markdown

Read-onlyIdempotent

Read one public web page. Use audit (default) for HTTP status, security-header grade, TLS and email DNS signals. Use markdown for page text, title, links and truncation status. Both modes fetch the supplied URL and follow public redirects.

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
urlYesAbsolute public HTTP or HTTPS page URL, e.g. https://example.org/. Use a URL accessible without credentials.
modeNoChoose audit for configuration signals or markdown to extract readable content.audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / mode / description
      Added value: +"Choose audit for configuration signals or markdown to extract readable content."
    • changedInput schema / properties / url / description
      Previous value: -"Public http/https URL"New value: +"Absolute public HTTP or HTTPS page URL, e.g. https://example.org/. Use a URL accessible without credentials."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: it performs a live fetch, follows public redirects, and surfaces truncation status in markdown mode, which tells the agent results may be incomplete.

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?

Three tight sentences, front-loaded with purpose followed by mode routing and shared fetch semantics. No filler and no repetition of structured fields.

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

Completeness4/5

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

With no output schema, describing per-mode return contents is exactly the right compensation, and truncation signaling covers a key failure mode. Missing only secondary details such as error behavior on unreachable URLs or rate limits.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes further by explaining what each mode value yields rather than just restating the enum. The url parameter's constraints (absolute, public, credential-free) are reinforced from the schema rather than newly clarified.

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?

The description opens with a specific verb and resource ('Read one public web page') and then splits the tool's two behaviors into named modes with distinct outputs (audit for HTTP status, security-header grade, TLS and email DNS; markdown for text, title, links, truncation). An agent knows exactly what the tool produces without opening the schema.

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

Usage Guidelines4/5

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

It gives explicit mode selection guidance and flags audit as the default, which is the main decision an agent faces here. It stops short of stating exclusions (e.g., what to do for credentialed or non-public pages) beyond the 'public'/'without credentials' framing carried in the schema.

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