Skip to main content
Glama

aeo-playbook

AEO playbook kit. The complete methodology for getting a site cited by answer engines: the five-stage retrieval pipeline, seven durable laws, graded tactic tiers, per-engine notes, a 90-day implementation plan, templates, and a citation measurement rig. One call returns the full kit. Price: $12.00 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

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the most consequential trait: this is a paid call at $12.00 in USDC on Base mainnet via x402, and an unpaid call returns HTTP 402 with machine-readable payment terms. That is genuinely useful for an agent deciding whether and how to invoke it. However, it says nothing about the shape of the successful response (format, size, whether it is paginated or reference text an agent can quote) or whether repeat calls are billed again.

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?

Two sentences, front-loaded with what the kit contains and back-loaded with the payment behavior an agent must know before calling. The long enumeration earns its place by telling the agent what it is buying, though it could be tightened without losing meaning.

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 the return value and does so by listing the kit's components. The payment/402 path is fully covered. The main remaining gap is response format and volume, which matters for a zero-parameter content-purchase tool whose entire value is the returned payload.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, so the baseline is 4 and there is nothing the description needs to disambiguate. The phrase 'one call returns the full kit' usefully confirms no options or filters exist, which prevents an agent from guessing at configuration parameters.

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 names a specific deliverable — a complete AEO methodology kit — and enumerates its contents (retrieval pipeline, laws, tactic tiers, per-engine notes, 90-day plan, templates, measurement rig). 'One call returns the full kit' makes the output model unambiguous, which distinguishes it from the sibling aeo-scan. The phrasing is noun-first rather than verb-first, so what the tool *does* is inferred from the return statement rather than stated up front.

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?

The description implies a use case ('for getting a site cited by answer engines') but never says when to call this versus alternatives such as aeo-scan, nor when not to call it. There is no prerequisite guidance (e.g., scan first, then buy the playbook) and no statement about whether results are static reference content or site-specific.

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