Skip to main content
Glama

site-audit

Crawls up to 25 pages of one website (same host only) and reports the problems an SEO or QA check looks for: broken links (up to 40 outbound links spot-checked per page), missing page titles and meta descriptions, slow pages over 1.5 seconds, and pages over 500 KB. Returns a summary of issues plus per-page details as JSON. Has a 45-second time limit and polite pacing. Every URL is fetched through a public-internet-only safe fetcher. Paid only: $0.50 per call via x402 at https://tools.orchardshop.xyz/t/site-audit.

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": "site-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYese.g. https://example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: crawl/page limits, outbound link spot-checking, performance thresholds, time limit, polite pacing, public-internet-only fetcher, and paid cost. It also notes the JSON return shape, making behavior unusually transparent.

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?

The definition is dense but front-loaded: capability, audit checks, limits, return format, safety, and payment are ordered sensibly. Every sentence adds operational information, with no filler.

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

Completeness5/5

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

For a one-parameter audit tool with no annotations or output schema, the description covers invocation context, operational limits, safety, cost, and return format. No critical decision-making information appears missing.

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?

The only parameter is documented in the schema at 100% coverage, so the baseline is 3. The description adds the crawl boundary ('same host only') and public-internet restriction, but does not add URL format or validation semantics beyond the schema example.

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 uses a specific verb and resource ('Crawls up to 25 pages of one website') and frames output as SEO/QA issue detection, which clearly separates it from crawl-to-markdown or metadata siblings. Scope and limits are stated up front.

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 identifies the use case (SEO or QA check) and constraints (one site, same host, 25 pages), giving clear context for when to use it. It does not explicitly name when not to use it or point to an alternative sibling, so it falls short of a 5.

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