Skip to main content
Glama
Sign In

AEORank — SEO, AEO & GEO Audit Engine

by app.aeorank
OverviewDiscussionsAdmin

Run Sandbox GEO-62 Diagnostic Preview

run_sandbox_audit
Read-onlyIdempotent

Execute an instant zero-latency ($0) AEORank GEO-62 & Agentic Web 2026 diagnostic preview for a domain or URL.

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

Input Schema

NameRequiredDescriptionDefault
urlYesTarget website URL or domain (e.g. https://example.com).
langNoOutput language ('en' or 'vi').

Output Schema

NameRequiredDescriptionDefault
okYes
trialYes
domainNo
sandboxNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description only needs to add context. It does add cost/latency claims ("zero-latency ($0)") and the preview/sandbox framing, but never explains whether the data returned is real, sampled, or simulated, or whether there are quotas — meaningful gaps for a diagnostic tool.

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?

A single sentence with no redundancy and the action front-loaded. It is efficient, though the stacked product/version jargon ("AEORank GEO-62 & Agentic Web 2026") consumes space without informing an agent.

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?

With an output schema present, return values need no explanation, and the tool is simple (2 params, read-only). Still missing is any statement of which diagnostics GEO-62 covers and what "sandbox" implies about result validity, which an agent needs to decide whether to rely on the output.

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 parameters are already documented in structured fields. The description only echoes the url parameter ("for a domain or URL") and says nothing about the lang enum or accepted URL formats, so it adds nothing beyond the schema; 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?

States a specific verb ("Execute ... diagnostic preview") and scope ("for a domain or URL"), which is enough to separate it from the sibling tools (patch packs, entity sources, rules, playbooks). The string of brand terms ("AEORank GEO-62 & Agentic Web 2026") obscures what the diagnostic actually checks, so the resource is named but not explained.

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

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance, no mention of how this differs from a full (non-preview) audit, and no hint about whether the "sandbox" result is authoritative or throwaway. The agent must infer usage entirely from the word "preview."

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

All AEORank — SEO, AEO & GEO Audit Engine toolsInspect
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