Skip to main content
Glama

aeo-scan

AEO scan. Any public domain in, an agent-readiness scorecard out, fetched live on the call: robots.txt with per-crawler AI access verdicts, content-signal lines, sitemap, llms.txt, landing metadata, markdown negotiation, and the well-known API catalog. Unreachable targets return their fetch outcomes as the result. Price: $0.05 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

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": "aeo-scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesThe public domain to scan for AI-answer readiness, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

With no annotations to lean on, the description carries the full burden and does so well: it discloses that fetching happens live on the call, that unreachable targets return their fetch outcomes rather than erroring, and that the tool is paid — $0.05 per call in USDC on Base mainnet over x402, with an unpaid call returning HTTP 402 plus machine-readable payment terms. These are exactly the behaviors an agent needs before invoking it.

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?

It is front-loaded correctly — what it is, input, output, then mechanics, then price — and every sentence carries information an agent needs. The middle enumeration of eight checks is dense but each item is substantive rather than 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?

For a one-parameter, annotation-free tool with no output schema, the description compensates by enumerating what the returned scorecard contains and by spelling out failure and payment behavior. The remaining gap is the shape of the scorecard itself (scoring scale, structure), which the description does not characterize.

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% with a single documented parameter, so the baseline is 3. The description adds modest meaning by stressing the target must be a public domain and by giving example.com as the format, but contributes no syntax, normalization, or protocol/host handling details beyond the schema.

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?

"AEO scan. Any public domain in, an agent-readiness scorecard out" gives a specific verb and resource plus an explicit input/output contract, and the follow-on sentence enumerates the concrete checks performed (robots.txt AI access verdicts, content-signal, sitemap, llms.txt, metadata, markdown negotiation, API catalog). It never names or contrasts with the sibling aeo-playbook, so an agent cannot tell from the description alone how this differs from that tool.

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?

The phrase "any public domain" implies a scope constraint (public targets only) and the live-fetch framing implies when it is appropriate, but there is no explicit when-to-use/when-not-to-use guidance and no alternative tool is named. Usage is inferable rather than stated.

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