SEO Audit

Local AI-search readiness

local_ai_readiness

Read-onlyIdempotent

Local-business readiness for AI search answers. Use this when the user asks if a local business site is ready to be named by AI search, ChatGPT, Gemini or similar, or what to fix so assistants can cite it. Pass the business's own site. Crawls only that site's public pages (robots.txt respected, up to 25, default 15) and returns pass, warn or fail for a page per service, location or service-area pages, visible prices, FAQ, LocalBusiness schema (name, address, phone, hours, geo, sameAs), NAP consistency, on-site proof, a one-line description and recent dated content. Each check has the evidence URL and a fix. Also returns what Gemini, OpenAI and Anthropic leaned on in a Yext study and profile advice, which is not fetched. It does not query AI engines, directories or review sites, or measure rankings. Not for a site with no physical location or service area: use audit_site. Do not use it for private addresses or to collect contact details.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	The business's own public site or page, for example example.com or https://example.com/contact. Only that site is crawled, starting from its homepage.
`max_pages`	No	Most pages to read, 1 to 25. Default 15.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`notes`	Yes
`study`	Yes
`checks`	Yes
`notice`	Yes
`engines`	Yes
`refused`	No
`summary`	Yes
`finalUrl`	No
`reachable`	Yes
`profileAdvice`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

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

Changed1 schema field changedOct 4, 2026

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

First observedOct 3, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), and the description still adds substantial operational context: crawl scope is one site's public pages, robots.txt is respected, the page cap is 25 with a default of 15, and it discloses that the study/profile advice is 'not fetched.' It also enumerates exactly what is returned per check (evidence URL and fix).

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?

Purpose and eligibility are front-loaded, and the dense middle section (checks returned, scoping caveats) earns its length by preventing misexecution. It is on the verbose side for a two-parameter tool, but nearly every clause carries routing or behavioral information.

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 read-only crawler, the description is complete: input scope, execution limits, the full set of returned checks, and explicit non-capabilities are all stated. Since an output schema exists, the description needn't expand further on return structure, and it is right not to.

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%, so the baseline is 3. The description adds marginal semantic value beyond the schema by instructing 'Pass the business's own site' and clarifying that crawling starts from the homepage and only that site is touched, reinforcing what the url parameter must be.

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 pairing ('Local-business readiness for AI search answers') and immediately names what it is not ('does not query AI engines, directories or review sites, or measure rankings'). It also distinguishes itself from the sibling audit_site by audience (local businesses with a physical location or service area). An agent can select this tool without opening any schema.

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?

Explicit when-to-use ('when the user asks if a local business site is ready to be named by AI search'), explicit alternative routing ('Not for a site with no physical location or service area: use audit_site'), and explicit exclusions (no private addresses, no contact-detail collection). Nothing 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.

All SEO Audit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.