Skip to main content
Glama

Site audit summary

site_audit_summary
Read-only

Pro. Score a site in one call. Crawls the site from url (same origin only, up to 40 pages, 4 requests at a time, or only the paths you list), uses sitemap.xml to find pages, and obeys robots.txt for the user agent ATPDesigners. Reads static HTML only. The result opens with coverage: pages read of pages found, which were skipped or truncated, and requests used. Runs the inventory, meta, heading and link health checks over the same crawl and returns a 0 to 100 score per area (each check has a weight; points lost are weight times the share of pages or links affected; the formula is printed in the result), an overall average, and the top 10 issues. Optional maxLinkChecks lowers the link check cap.

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

Input Schema

NameRequiredDescriptionDefault
urlYesHome page or any page on the site. The crawl stays on this origin.
pathsNoOptional list of same-origin paths such as /about. When given, only these pages are read and links are not followed.
sitemapNoUse sitemap.xml to find pages. Default true.
maxPagesNoOptional lower page cap. The hard cap is 40 pages.
maxLinkChecksNoOptional lower cap on extra link requests. The hard cap is 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior5/5

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

With only read-only/open-world/non-destructive annotations, the description adds substantial behavioral detail: same-origin crawling, up to 40 pages, 4 concurrent requests, sitemap discovery, robots.txt obedience, static HTML only, and a coverage summary in the result. It also explains score computation and what is returned, far beyond the annotations.

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 description is dense but well sized for a complex crawler and scorer, with the core purpose front-loaded. 'Pro.' is an unexplained opener, but the rest of the prose is information-rich rather than repetitive.

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?

Despite having no output schema, the description explains the result shape: coverage summary, skipped/truncated pages, requests used, per-area scores, overall average, and top 10 issues. That is enough for an agent to understand both invocation and return semantics.

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 description coverage is 100%, so the schema already defines all five parameters. The description reinforces `url`, `paths`, `sitemap`, and `maxLinkChecks` behavior but adds little beyond the schema text; the baseline of 3 applies when the schema does the parameter documentation.

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?

States a specific verb and resource: score a site in one call, using a crawl and four named check families. The phrase 'in one call' plus the listed inventory/meta/heading/link checks distinguishes this aggregate scorer from the individual sibling site audit tools.

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

Usage Guidelines3/5

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

Usage context is implied by 'Score a site in one call' and by the `paths` behavior, but there is no explicit guidance on when to choose this over sibling tools such as `site_inventory` or `site_link_health`. The agent can infer it is the aggregate option, but alternatives are not named or excluded.

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