Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Is this site ready for AI agents in one call: robots.txt AI-bot rules, llms.txt, agent-card.json, openapi.json, x402 wel

ai_readiness
Read-onlyIdempotent

Is this site ready for AI agents in one call: robots.txt AI-bot rules, llms.txt, agent-card.json, openapi.json, x402 well-known, MCP server card, readiness score (url=https://example.com). Live requests, public hosts only. Pay per call $0.002 USDC on Base via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ai_readiness"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNosite or origin to check
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, and non-destructive behavior, yet the description adds genuinely new context: live network requests are made against the target, only public hosts are permitted, and each call costs $0.002 USDC on Base via x402. It stops short of describing rate limits, failure modes for unreachable hosts, or response shape, which keeps it below 5.

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 definition is front-loaded with the core question and then lists the concrete checks, with cost and host constraints last. It is a single dense line with little waste, though the long comma-separated checklist reads more like a title than flowing prose.

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

Completeness3/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 carries the burden of describing what comes back; it mentions a 'readiness score' and the individual checks but not the response structure or what happens when artifacts are missing. For a multi-source scanning tool with a paid flow, that is an adequate but incomplete picture.

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%, so both url and x_payment are already documented, including the first-call payment handshake. The description only adds a format hint with the '(url=https://example.com)' example; the schema remains the primary source of parameter meaning.

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?

The description names a specific verb-and-resource job ('Is this site ready for AI agents… robots.txt AI-bot rules, llms.txt, agent-card.json, openapi.json, x402 well-known, MCP server card, readiness score') and the enumeration of checks clearly separates it from siblings like url_status, security_headers, or page_meta. An agent can tell exactly what this returns without opening the 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?

It provides constraints ('Live requests, public hosts only') and implies the value proposition ('in one call'), which hints this replaces several single-purpose checks. However, it never names an alternative tool or states an explicit when-not-to-use condition beyond the public-hosts restriction, so routing guidance is only implied.

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