Skip to main content
Glama

Managed Nerds

check_ai_readiness

Read-onlyIdempotent

Free AI search readiness check for a website (also accepts a domain or email address): whether ChatGPT, Claude, Perplexity, Google's AI Overviews, Bing and Copilot, Apple (Siri, Spotlight) and Meta AI can find and read it. Reads robots.txt by crawler job (search crawlers are graded; training crawlers are the owner's choice and only noted, since each company uses separate names), the home page (noindex, nosnippet, text without JavaScript, business structured data, title and description), the sitemap and llms.txt. Grades it (good, needs work, at risk) with exactly what to fix. Public data only, about four requests to the site; it never pretends to be a crawler, so firewall blocks can't be seen. No contact details; the domain and result are kept 90 days, nothing about who asked. 10 checks an hour per address.

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

Input Schema

NameRequiredDescriptionDefault
domainYesexample.com, https://example.com or you@example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Well beyond the supplied annotations, the description discloses cost (free), data sources (public data only), request volume (~four requests), a real limitation (it does not impersonate a crawler, so firewall blocks are invisible), a privacy/data-retention policy (domain and result kept 90 days, no requester identity), and a rate limit (10 checks/hour per address). It also explains the grading nuance between search crawlers and training crawlers, which is meaningful interpretive context an agent could not otherwise know.

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 purpose and then layered with what is checked, how it is graded, its limits, and its privacy posture; every clause carries information. The long parenthetical enumerating AI providers is slightly dense but remains scannable and relevant.

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?

With no output schema, the description still conveys the shape of the result (a three-level grade plus exactly what to fix), and it preempts the main caller questions: scope of inputs, cost, privacy, rate limits, and known blind spots. Nothing essential for a correct invocation appears to be 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 description coverage is 100% and the single parameter already documents the accepted forms (example.com, https://example.com, you@example.com). The description restates that an email address is accepted but adds no new syntax, normalization, or validation detail, so the baseline of 3 applies.

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 and resource: a free AI search readiness check for a website/domain/email, and enumerates exactly what is inspected (robots.txt per crawler job, home page signals, sitemap, llms.txt) and what is produced (a good/needs work/at risk grade). This is clearly distinguishable from sibling checks like check_domain, check_email_security, or request_seo_check 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the 'Free' framing plus 'also accepts a domain or email address' signals it is a quick self-serve check, and the rate limit hints at lightweight exploratory use. However, it never explicitly says when to use this versus a sibling such as check_domain or request_seo_check, or when a result is insufficient and a deeper/paid request is warranted.

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.

Resources