Free AI readiness scan for any website. Paid reports for agents are coming soon.
Scored across 1 tool
With only one tool, there is no possibility of confusion or misselection. An agent will always know to call scan_site for any site-checkup task.
scan_site follows a clear verb_noun snake_case convention. With a single tool there are no competing conventions to introduce inconsistency.
A single tool is on the thin side, but it is deliberately comprehensive—bundling robots.txt, llms.txt, JSON-LD, meta, HTML, and sitemap checks into one scan. For a focused 'checkup' server this scoping is reasonable, though someone wanting granular per-check results might prefer separate tools.
The tool covers the full AI-crawler readiness surface: crawler rules, llms.txt, structured data, metadata, raw HTML content, and sitemap, with scoring and prioritized fixes. No obvious gaps for the stated purpose.
Free. Checks a website's robots.txt rules for AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, CCBot), llms.txt, schema.org JSON-LD, title and meta description, content in raw HTML, and sitemap. Returns a 0 to 100 score and prioritized fixes.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Website URL, e.g. https://example.com |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It discloses the tool's scope (read-only inspection of publicly served files), that it is free, the exact checks performed, and the return shape (0-100 score plus prioritized fixes). It stops short of noting rate limits, auth requirements, or behavior on unreachable/invalid URLs, so it is strong but not exhaustive.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with cost and scope, with zero filler. The parenthetical crawler list is long but earns its place by specifying exactly which bots are evaluated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description correctly explains the return value (0-100 score, prioritized fixes), which is the key missing structured information. Only minor gaps remain: failure modes for invalid/unreachable URLs and any invocation constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Single parameter with 100% schema coverage, so the schema already documents the accepted URL format. The description adds nothing about URL syntax or constraints, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ("Checks") and resource (a website's AI-readiness surfaces: robots.txt AI-crawler rules, llms.txt, JSON-LD, meta, raw HTML content, sitemap). An agent can immediately tell this is a site-readiness audit and what each check targets.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No statement of when to use it, what prerequisites exist, or when-not to use it. The word "Free" hints at no-cost/no-auth, but there is no explicit context for selecting this tool or any exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
scan_site
Add one secure layer between your agents and this server.