Skip to main content
Glama

agent_readiness_scan

Read-only

Free check of how readable and usable a public website is for AI agents: llms.txt, robots.txt AI-crawler rules, sitemap, schema.org JSON-LD, MCP and x402 discovery, OpenAPI, and whether the page is readable without JavaScript. Returns a 0-100 score, a grade, and a fix list. Rate-limited to 10 scans per IP per UTC day. No payment and no API key.

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": {
      "url": "<url>"
    },
    "name": "agent_readiness_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the site or page to scan

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, non-destructive, open-world), but the description adds genuinely non-derivable behavior: rate limiting tied to IP per UTC day, no authentication or payment required, and the shape of the result (0-100 score, grade, fix list). It does not say what happens for unreachable or non-public URLs, or how long a scan takes.

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 core purpose, followed by the inspected artifact list, then returns and limits. The long enumeration is dense but each item is informative; wording is tight with no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description usefully summarizes the return (score, grade, fix list) and covers cost/rate/auth constraints. For a single-parameter read-only scan this is nearly complete, with only edge-case behavior for invalid or unreachable URLs left unstated.

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 coverage is 100% and the single url parameter is already documented with an example, so the schema carries the load. The description adds only a scope constraint — the URL must be a public http(s) site or page — rather than format or syntax detail, which matches the baseline for high-coverage schemas.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific action (scan a public website) and enumerates the exact artifacts inspected: llms.txt, robots.txt AI-crawler rules, sitemap, schema.org JSON-LD, MCP/x402 discovery, OpenAPI, and JS-free readability. That enumeration makes it clearly distinct from siblings like read_url or page_links, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives clear operating context: it applies to public http(s) sites or pages, is free, needs no API key, and is capped at 10 scans per IP per UTC day. It offers no explicit when-not-to-use guidance or named alternative for related tasks, which keeps it below a 5.

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