Skip to main content
Glama

Site SEO & AI Crawler Audit

Check AI readiness of a store or page

ai_readiness_check
Read-onlyIdempotent

Checks if AI agents can read and cite a store or page. Use it when the user asks whether AI agents can read an online store or cite a page, for example "does shop.example.com have an llms.txt?" or "will AI assistants cite this page?". Pass url for a page or domain for the domain files only; one is enough. Returns whether the domain has /llms.txt, /agents.md, the UCP file at /.well-known/ucp (version and services shown) and /sitemap.xml, and which of 14 AI crawlers robots.txt blocks site-wide. With a page address it also rates five citation signals (summary near the top, author credentials, Q&A format, heading structure, structured data) as pass, warn or fail with evidence and a fix. It requests at most five domain files and one page, skips what robots.txt disallows for Agent Tools, and shows what is published, not whether an agent can buy. Do not use it for private or local addresses, to read page content, or to scan for vulnerabilities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoAddress of one public web page, for example https://example.com/blog/guide. Pass url or domain, not both needed. With url the page is rated for five AI citation signals and its domain files are checked too. A bare domain means https.
domainNoHost name of a public store or website, for example shop.example.com. Pass url or domain, not both needed. With domain only the domain files are checked (llms.txt, agents.md, UCP, sitemap, AI crawler rules).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
ucpNo
pageNo
notesNoPlain-language caveats to pass on with the result.
domainYesHost checked.
noticeYesAs-of caveat: what the site sent to Agent Tools at that moment, not what every agent sees.
originNoOrigin the domain files were read from, after redirects.
robotsNo
sourceYesWhere the data came from: the website itself.
failureNoWhy the site or page was not reached or read, such as a timeout or a robots.txt disallow for Agent Tools.
llmsTxtNo
missingNoDomain files that were not found.
presentNoDomain files that were found.
sitemapNo
agentsMdNo
platformNoshopify when Shopify headers were seen.
reachableYesFalse when the site did not answer; failure then says why.
citationChecksNo
citationSummaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed40 schema fields changed
    • addedInput schema / minProperties
      Added value: +1
    • changedInput schema / properties / domain / description
      Previous value: -"Domain of a public store or website, for example shop.example.com. Used when checking domain files only (llms.txt, agents.md, UCP, sitemap, AI crawler rules)."New value: +"Host name of a public store or website, for example shop.example.com. Pass url or domain, not both needed. With domain only the domain files are checked (llms.txt, agents.md, UCP, sitemap, AI crawler rules)."
    • changedInput schema / properties / url / description
      Previous value: -"Address of one public web page to check for AI citation signals (clear summary, author credentials, Q&A format, heading structure, structured data), for example https://example.com/blog/guide. A bare domain means https. When provided, the page is checked for citation signals alongside domain files."New value: +"Address of one public web page, for example https://example.com/blog/guide. Pass url or domain, not both needed. With url the page is rated for five AI citation signals and its domain files are checked too. A bare domain means https."
    • addedOutput schema / properties / agentsMd / properties / finalUrl / description
      Added value: +"Address of the file after redirects."
    • addedOutput schema / properties / agentsMd / properties / found / description
      Added value: +"True when the file answered 2xx with the expected kind of content."
    • addedOutput schema / properties / agentsMd / properties / links / description
      Added value: +"Number of http(s) Markdown links in the file."
    • addedOutput schema / properties / agentsMd / properties / skipped / description
      Added value: +"Why the file was not requested, such as a robots.txt disallow for Agent Tools."
    • addedOutput schema / properties / agentsMd / properties / status / description
      Added value: +"HTTP status code of the file."
    • addedOutput schema / properties / agentsMd / properties / title / description
      Added value: +"First Markdown heading of the file."
    • addedOutput schema / properties / domain / description
      Added value: +"Host checked."
    • addedOutput schema / properties / failure / description
      Added value: +"Why the site or page was not reached or read, such as a timeout or a robots.txt disallow for Agent Tools."
    • addedOutput schema / properties / llmsTxt / properties / finalUrl / description
      Added value: +"Address of the file after redirects."
    • addedOutput schema / properties / llmsTxt / properties / found / description
      Added value: +"True when the file answered 2xx with the expected kind of content."
    • addedOutput schema / properties / llmsTxt / properties / links / description
      Added value: +"Number of http(s) Markdown links in the file."
    • addedOutput schema / properties / llmsTxt / properties / skipped / description
      Added value: +"Why the file was not requested, such as a robots.txt disallow for Agent Tools."
    • addedOutput schema / properties / llmsTxt / properties / status / description
      Added value: +"HTTP status code of the file."
    • addedOutput schema / properties / llmsTxt / properties / title / description
      Added value: +"First Markdown heading of the file."
    • addedOutput schema / properties / missing / description
      Added value: +"Domain files that were not found."
    • addedOutput schema / properties / notes / description
      Added value: +"Plain-language caveats to pass on with the result."
    • addedOutput schema / properties / notice / description
      Added value: +"As-of caveat: what the site sent to Agent Tools at that moment, not what every agent sees."
    • addedOutput schema / properties / origin / description
      Added value: +"Origin the domain files were read from, after redirects."
    • addedOutput schema / properties / platform / description
      Added value: +"shopify when Shopify headers were seen."
    • addedOutput schema / properties / present / description
      Added value: +"Domain files that were found."
    • addedOutput schema / properties / reachable / description
      Added value: +"False when the site did not answer; failure then says why."
    • addedOutput schema / properties / robots / properties / httpStatus / description
      Added value: +"HTTP status code of robots.txt."
    • addedOutput schema / properties / robots / properties / sitemaps / description
      Added value: +"Sitemap addresses listed in robots.txt."
    • addedOutput schema / properties / robots / properties / status / description
      Added value: +"found: rules were read. missing: a 4xx answer, so nothing is restricted. unreachable: a 5xx or no answer, so no other file or page was requested."
    • addedOutput schema / properties / sitemap / properties / finalUrl / description
      Added value: +"Address of the file after redirects."
    • addedOutput schema / properties / sitemap / properties / found / description
      Added value: +"True when the file answered 2xx with the expected kind of content."
    • addedOutput schema / properties / sitemap / properties / links / description
      Added value: +"Number of http(s) Markdown links in the file."
    • addedOutput schema / properties / sitemap / properties / skipped / description
      Added value: +"Why the file was not requested, such as a robots.txt disallow for Agent Tools."
    • addedOutput schema / properties / sitemap / properties / status / description
      Added value: +"HTTP status code of the file."
    • addedOutput schema / properties / sitemap / properties / title / description
      Added value: +"First Markdown heading of the file."
    • addedOutput schema / properties / source / description
      Added value: +"Where the data came from: the website itself."
    • addedOutput schema / properties / ucp / properties / finalUrl / description
      Added value: +"Address of the file after redirects."
    • addedOutput schema / properties / ucp / properties / found / description
      Added value: +"True when the file answered 2xx with the expected kind of content."
    • addedOutput schema / properties / ucp / properties / links / description
      Added value: +"Number of http(s) Markdown links in the file."
    • addedOutput schema / properties / ucp / properties / skipped / description
      Added value: +"Why the file was not requested, such as a robots.txt disallow for Agent Tools."
    • addedOutput schema / properties / ucp / properties / status / description
      Added value: +"HTTP status code of the file."
    • addedOutput schema / properties / ucp / properties / title / description
      Added value: +"First Markdown heading of the file."
  2. Changed1 schema field changed
    • removedOutput schema / properties / note_from_openkrill
      Removed value: -{
      -  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      -  "type": "string"
      -}
  3. Changed1 schema field changed
    • addedOutput schema / properties / note_from_openkrill
      Added value: +{
      +  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
      +  "type": "string"
      +}
  4. Changed6 schema fields changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain of a public store or website, for example shop.example.com. Only the host is used. A full address is accepted and reduced to its host."New value: +"Domain of a public store or website, for example shop.example.com. Used when checking domain files only (llms.txt, agents.md, UCP, sitemap, AI crawler rules)."
    • addedInput schema / properties / url
      Added value: +{
      +  "description": "Address of one public web page to check for AI citation signals (clear summary, author credentials, Q&A format, heading structure, structured data), for example https://example.com/blog/guide. A bare domain means https. When provided, the page is checked for citation signals alongside domain files.",
      +  "maxLength": 2048,
      +  "minLength": 3,
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "domain"
      -]
    • addedOutput schema / properties / citationChecks
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "evidence": {
      +        "type": "string"
      +      },
      +      "fix": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "enum": [
      +          "summary_clarity",
      +          "author_credentials",
      +          "qa_format",
      +          "heading_structure",
      +          "structured_data"
      +        ],
      +        "type": "string"
      +      },
      +      "status": {
      +        "enum": [
      +          "pass",
      +          "warn",
      +          "fail"
      +        ],
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "status",
      +      "title",
      +      "evidence",
      +      "fix"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / citationSummary
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "fail": {
      +      "type": "integer"
      +    },
      +    "pass": {
      +      "type": "integer"
      +    },
      +    "warn": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "pass",
      +    "warn",
      +    "fail"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / page
      Added value: +{
      +  "properties": {
      +    "blockedByRobots": {
      +      "type": "boolean"
      +    },
      +    "failure": {
      +      "type": "string"
      +    },
      +    "finalUrl": {
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "type": "integer"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds real behavioral context beyond them: it requests at most five domain files and one page, skips what robots.txt disallows for Agent Tools, and explicitly scopes the result to what is published rather than whether an agent can transact.

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 purpose and scope, then usage, then returns, then exclusions — a logical order. It is on the long side with quoted example queries, but each sentence carries distinct information and nothing is 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 two-parameter read-only checker, the description covers trigger conditions, parameter behavior, expected outputs, operational limits, and explicit out-of-scope cases. An output schema exists, so the brief return summary is a bonus rather than a necessity, and nothing needed to invoke it correctly is 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?

Schema coverage is 100% and both parameters already document the url/domain distinction and mutual exclusivity, so the description largely restates the schema. It adds the useful framing that passing url also triggers domain-file checks and page rating, but not enough to exceed the baseline for fully documented parameters.

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 (checks) and resource (AI readability/citability of a store or page), and names the exact artifacts examined (llms.txt, agents.md, UCP, sitemap, robots.txt crawler rules, five citation signals). This clearly separates it from siblings like check_ai_crawler_access and check_page_tags.

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?

Gives concrete user phrasings that should trigger it, explains the url-vs-domain choice, and lists explicit exclusions: no private/local addresses, not for reading page content, not for vulnerability scanning. When-to-use and when-not-to-use are both present.

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.