Skip to main content
Glama

AnswerRail AEO, Schema.org & /llms.txt Audit MCP

Audit Live Website AI Crawler & Lighthouse 13.5 Readiness

audit_ai_readiness
Read-onlyIdempotent

Audits a live website URL or domain for AI crawler access (GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot), 25,000-token HTML RAG truncation, /llms.txt presence, Schema.org JSON-LD entities, and Google Lighthouse 13.5 /.well-known/ai-catalog.json compliance. Returns a structured Markdown diagnostic report containing a 0-100 AI Readiness Score, letter grade, raw-vs-clean token counts, per-check pass/fail status, and remediation links. Use this tool first when diagnosing why a live website is omitted by ChatGPT, Perplexity, or Claude; do not use it to extract full-page Markdown text (use extract_byte0_markdown instead), to synthesize manifest previews (use generate_ai_manifests instead), or to inspect local disk files (use audit_local_codebase instead). Bare domains automatically resolve to https:///, and deep URLs audit the exact page weight while checking /robots.txt and /.well-known/ai-catalog.json at the origin root. Read-only HTTP check; requires no API key, allows up to 60 requests/min, and returns a timeout message if the origin fails to respond within 8 seconds.

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

Input Schema

NameRequiredDescriptionDefault
urlYesFully qualified HTTPS URL or bare domain name to audit (e.g., "https://stripe.com/pricing" or "example.com"). Defaults to HTTPS if scheme is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false, idempotentHint, openWorldHint), and the description adds genuinely new operational facts: no API key required, a 60 requests/min rate limit, an 8-second timeout message on origin failure, bare-domain-to-HTTPS resolution, and the origin-root scope for /robots.txt and ai-catalog.json. It also describes the shape of the returned report rather than leaving output opaque.

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 text is front-loaded with purpose, then scope rules, then exclusions, then operational constraints — a sensible ordering. It is dense in a single paragraph and some check-detail listing could be trimmed, but every clause carries information an agent would otherwise have to guess.

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?

With no output schema, the description compensates by specifying the returned Markdown report contents (0-100 score, letter grade, token counts, per-check pass/fail, remediation links). Combined with the timeout and rate-limit notes, an agent has everything needed to call this correctly and interpret results.

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% for the single `url` parameter, so the baseline applies, but the description still adds behavioral meaning the schema lacks: bare domains resolve to https://<domain>/, while deep URLs audit exact page weight yet check robots.txt and /.well-known/ai-catalog.json at the origin root. That scope distinction is a real semantic addition.

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+resource ("Audits a live website URL or domain") and enumerates the concrete checks performed — crawler access for named bots, RAG truncation, /llms.txt, JSON-LD, Lighthouse 13.5 — so an agent knows exactly what this tool produces and can distinguish it from siblings like extract_byte0_markdown or generate_ai_manifests.

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

Usage Guidelines5/5

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

It gives an explicit "use this tool first when diagnosing why a live website is omitted by ChatGPT, Perplexity, or Claude" trigger plus three named exclusions with the correct alternative for each (Markdown extraction, manifest synthesis, local disk inspection). Nothing about when-to-use is left to inference.

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.