AEO Inspector

domain_report

Read-only

One-domain report: runs the OrionCMD site audit (TLS from CT logs, DNS/DNSSEC/CAA, RDAP expiry, SPF/DMARC/DKIM/MTA-STS, security headers, security.txt) and the AEO Inspector deep scan (AI crawler access, bot-vs-browser diff, agent-ready checks) for one domain. Returns both grades and one merged, priority-sorted fixes list (paste-ready DNS records, registrar steps, robots.txt/llms.txt/JSON-LD) with a shell command to verify each, plus a report_url kept 30 days. Not charged if any part can't run. Costs $2 USDC per call via x402 (payment in _meta["x402/payment"]); invalid input or a failed run returns an error and is not charged.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Website or page URL, e.g. example.com

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, it discloses meaningful behavioral details: $2 USDC cost via x402, payment location in _meta, no charge if any part cannot run, no charge for invalid input or failed runs, and a report_url retained for 30 days. These details go well beyond what readOnlyHint and openWorldHint provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the tool's purpose, then presents outputs, charging behavior, and payment mechanics in a compact sequence. Despite the parenthetical audit lists, every clause conveys useful scope or operational information.

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

Completeness5/5

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

Given the tool's complexity and lack of an output schema, the description is complete: it explains the audits performed, the returned grades and fixes, report_url retention, payment cost and mechanism, and failure charging behavior. An agent has enough information to decide and invoke correctly.

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?

The schema already fully documents the single url parameter with format guidance, and the description only adds that the domain is singular. It does not add syntax or format details beyond the schema, so the baseline score for 100% coverage is appropriate.

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 specifies a clear verb and resource: running a one-domain site audit and AEO deep scan, then returning merged grades and fixes. It explicitly scopes the tool to one domain, which distinguishes it from the sibling full_report tool.

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?

The description clearly establishes usage context as a one-domain report and notes cost and charging behavior, but it does not explicitly name alternatives such as full_report or scan_site or state when not to use this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AEO Inspector tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?