Skip to main content
Glama

How readable is a website for AI agents? Checks llms.txt and llms-full.txt, AI c

ai_readiness
Read-only

How readable is a website for AI agents? Checks llms.txt and llms-full.txt, AI crawler rules in robots.txt, sitemap, JSON-LD, whether content renders without JavaScript, OpenAPI, MCP and x402 manifests, with a 0-100 score and fixes. Takes 2-5 s. Free: 20 calls/day per user across free tools, no payment needed. Above that: $0.003 per call (x402, USDC on Base).

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by disclosing latency (2-5 s), a per-user rate limit (20 calls/day across free tools), and the x402/USDC pricing trigger above that quota. It also states the output shape ('0-100 score and fixes'). What it omits is what an unpaid call returns or how failures surface, though the schema partially covers that.

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?

The scope list is front-loaded immediately after the framing question, so an agent learns what is checked before the cost details. The pricing sentences are longer than necessary but still earn their place for a paid tool. The title largely duplicates the opening sentence, which is the only clear waste.

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?

With no output schema, the description takes on the job of describing returns and does so at a coarse level ('0-100 score and fixes'). Combined with full parameter documentation and stated latency and cost, an agent has enough to decide to call it and to handle the payment flow. A little more on what 'fixes' contains would close the remaining gap.

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%, so both 'url' and 'payment' are already documented in structured form, including the instruction to omit payment on the first call. The description adds no constraints beyond the schema (e.g. no note on URL normalization or http-only requirements), so the baseline 3 applies.

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?

The description states a specific verb and resource ('how readable is a website for AI agents') and enumerates the artifacts it inspects (llms.txt, llms-full.txt, robots.txt crawler rules, sitemap, JSON-LD, no-JS rendering, OpenAPI, MCP, x402). That is far more specific than the sibling names 'sitemap' or 'robots' would suggest. It stops short of explicitly contrasting itself with those overlapping single-artifact siblings, which keeps it at a 4.

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 context is implied by the scope list ('AI readiness audit of one URL'), and the text supplies practical operating conditions — 2-5 s runtime, a 20 calls/day free tier, and the paid fallback. However, it never says when to pick this over the narrower sibling checks like sitemap or robots, nor whether it is meant as a one-shot audit versus a component check.

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.