Skip to main content
Glama

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

Generate /llms.txt & Lighthouse 13.5 ai-catalog.json Previews

generate_ai_manifests
Read-onlyIdempotent

Synthesizes a 6-line /llms.txt documentation index preview and a Google Lighthouse 13.5 /.well-known/ai-catalog.json (ARD 1.0) JSON preview from a live remote domain, returning both code blocks in Markdown alongside remediation links. Use this tool when a user wants to preview the discovery manifests needed to fix gaps found by audit_ai_readiness on a live domain; do not use it for full-page content extraction (use extract_byte0_markdown instead) or local filesystem inspection (use audit_local_codebase instead). If a full URL path is passed in domain, the generator automatically normalizes it to the registrable origin root before synthesizing root-level /llms.txt and /.well-known/ai-catalog.json URIs. Read-only synthesis that never modifies remote servers or local files; requires no API key, has a 60 req/min rate limit, and falls back to baseline origin metadata if the target blocks crawlers.

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": {
      "domain": "<domain>"
    },
    "name": "generate_ai_manifests"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesTarget domain name or root URL to generate manifest previews for (e.g., "example.com" or "https://example.com"). Path segments are stripped to the origin root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Target domain name or root URL to generate manifests for (e.g., \"example.com\" or \"https://example.com\")."New value: +"Target domain name or root URL to generate manifest previews for (e.g., \"example.com\" or \"https://example.com\"). Path segments are stripped to the origin root."
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing no API key requirement, a 60 req/min rate limit, fallback to baseline origin metadata when crawlers are blocked, and automatic normalization of a full URL path to the registrable origin root. The annotations already cover read-only/idempotent/non-destructive, so these operational details are the real added value; only the exact fallback content shape is left implicit.

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?

Front-loaded with the core action and return format, then usage exclusions, then operational caveats. Dense but every sentence carries information; the first sentence is long and packs both outputs plus the return format, which slightly slows scanning.

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?

No output schema exists, yet the description specifies the return value (both code blocks in Markdown plus remediation links). For a one-parameter, read-only, open-world tool, the purpose, routing, limits and fallback behavior are all covered.

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% with a single well-documented parameter, so baseline is 3; the description adds meaning by explaining that path segments are stripped to the origin root and that root-level /llms.txt and /.well-known/ai-catalog.json URIs are then synthesized, which tells the agent what a full URL input actually does.

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 specific verbs and resources: synthesizes a 6-line /llms.txt index preview and a Lighthouse 13.5 /.well-known/ai-catalog.json (ARD 1.0) preview from a live remote domain, and names the return format. It distinguishes itself from audit_ai_readiness, extract_byte0_markdown and audit_local_codebase by name.

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?

Explicitly says when to use it (previewing discovery manifests to fix gaps found by audit_ai_readiness on a live domain) and when not to, naming both alternatives with the conditions that select them (full-page content extraction, local filesystem inspection).

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.