Exepal

Agent-readiness check

agent_ready

Read-onlyIdempotent

Agent-readiness check for a website: robots.txt access for 19 AI crawlers (search, assistant and training bots from OpenAI, Anthropic, Google, Perplexity, Apple, Meta and others), sitemap, llms.txt, server-rendered text, structured data, meta robots and agent endpoints (MCP server card, A2A agent card, x402, OpenAPI), with a 0-100 score, grade and fixes. Use when someone asks whether AI assistants (ChatGPT, Claude, Perplexity, Gemini) can find, read and cite their site, why they do not show up in AI answers, whether they block AI crawlers, or before an agent crawls a site to see which bots it allows. Pass domain (a URL or email is reduced to its host). Returns score 0-100, grade A-F, checks[] {id, label, pass, points, max, detail}, robots {bots[] {bot, company, purpose (search, user-fetch, training), access (allowed, partial, blocked)}, summary, sitemaps, contentSignals}, sitemap, llmsTxt, homepage {wordCount, needsJs, structuredData, metaRobots}, agentEndpoints, liveFetch (home page loaded as Chrome and as ChatGPT-User, OAI-SearchBot, Claude-User, PerplexityBot, Perplexity-User; blockedBots lists bots a firewall turns away) and plain-language recommendations[]. Fetches the site directly; not charged when the site does not answer. For DNS and email security use domain; for whether AI assistants actually recommend the brand use ai_visibility_quick. Price: $0.005 per call from Exepal credit; not charged if the call fails. Includes free daily calls.

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

Input Schema

Name	Required	Description	Default
`domain`	Yes	Website to check, e.g. stripe.com or https://www.example.com (only the host is used)

Output Schema

Name	Required	Description
`url`	No
`grade`	No	A, B, C, D or F
`score`	No	0-100
`cached`	No	Present and true when the answer came from Exepal's cache
`checks`	No
`domain`	No
`robots`	No
`llmsTxt`	No
`sitemap`	No
`summary`	No
`homepage`	No
`fetchedAt`	No
`liveFetch`	No
`agentEndpoints`	No
`recommendations`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

addedOutput schema / properties / liveFetch

Added value: +{
+  "properties": {
+    "blockedBots": {
+      "description": "Bots answered with an error while a normal Chrome request loaded: a firewall or bot-protection rule, not robots.txt.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "bots": {
+      "items": {
+        "properties": {
+          "bot": {
+            "type": "string"
+          },
+          "company": {
+            "type": "string"
+          },
+          "error": {
+            "type": "string"
+          },
+          "ok": {
+            "type": "boolean"
+          },
+          "status": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "browser": {
+      "properties": {
+        "error": {
+          "type": "string"
+        },
+        "ok": {
+          "type": "boolean"
+        },
+        "status": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

AddedNov 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Goes well beyond the annotations (readOnly, openWorld, idempotent) by disclosing that it fetches the site directly, that liveFetch loads the home page under multiple bot user agents, that blockedBots reveals firewall denials, and the billing behavior ($0.005 per call, not charged if the site does not answer or the call fails, free daily calls). Only the return-value enumeration is somewhat redundant with the output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and there is little pure filler, but the middle section is a long single-block enumeration of return fields that duplicates the existing output schema, and the heavy parenthetical nesting makes it a wall of text rather than a scannable structure.

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, open-world check tool with one parameter, the description covers purpose, usage triggers, sibling alternatives, fetching behavior, pricing/failure semantics and output expectations. An agent has everything needed to decide and invoke correctly.

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% and the single parameter is already documented, so the baseline is 3; the description adds a small amount of meaning by noting 'a URL or email is reduced to its host', which extends beyond the schema's URL-only example.

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?

Names a specific verb and resource ('Agent-readiness check for a website') and enumerates exactly what is inspected: robots.txt access for 19 AI crawlers, sitemap, llms.txt, server-rendered text, structured data, meta robots and agent endpoints, plus the 0-100 score/grade output. It is instantly distinguishable from siblings like 'domain' and 'read'.

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 trigger conditions ('Use when someone asks whether AI assistants can find, read and cite their site... before an agent crawls a site to see which bots it allows') and explicitly routes to alternatives: 'For DNS and email security use domain; for whether AI assistants actually recommend the brand use ai_visibility_quick.'

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Exepal 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.

Resources

Need Help?