agent-readiness

Reviewed 23h ago.

• tools: 5 tools scanned
• metadata: scanned

No findings.

Tools (5)

• score_site

  Use this when the user asks whether a website is ready for AI agents, agent-ready, AI-agent friendly or WebMCP-ready, or what to fix so agents can use it. Scores one public website out of 100 for agent readiness and returns a grade, the fitness and adoption sub-scores, the five highest-value fixes, the scan time and whether the result came from cache. Reads one public page plus standard discovery files (robots.txt, /.well-known endpoints, sitemaps, llms.txt) and up to ten same-origin script bundles; it never logs in, submits forms or changes the site. Results are cached for about an hour.

• explain_check

  Use this when the user asks what a specific Agent Readiness finding means, why it matters to AI agents or how to fix it, usually after score_site. Explains one check: what it asks, why an agent cares, how it is weighted and how to fix it, with a code snippet where one exists. Answers from the rule set only and fetches nothing.

• list_checks

  Use this when the user asks what the Agent Readiness Score measures or how it is calculated, rather than how one site performs. Lists every check in the rule set with its pillar, weight and question. Fetches nothing.

• get_badge_embed

  Use this when the user wants to show a site's Agent Readiness badge on that site. Scores the site if needed, then returns the HTML snippet for sites at grade C or better (bronze, silver or gold), or the reason and the first fixes when the site is not eligible. Returns HTML to paste; it installs nothing and runs no script.

• watch_site

  Use this only when the user explicitly asks to be emailed when a site's Agent Readiness Score changes. Sends a confirmation email for monitoring that site. Use only when the user explicitly asks to receive a confirmation email for monitoring at the supplied address. Set sendConfirmationEmail to true only then. Monitoring starts only after the recipient opens the link and confirms on the page; this call itself sends one email.