Skip to main content
Glama

playbook_x402_seller

Guides you to become an x402 seller on Cloudflare Workers, with a free demo TOC and excerpt, and paid access costing 3 USDC on Base per call.

Instructions

Playbook: become an x402 seller on Cloudflare Workers. Concise guide from Forge Agent Hub's own Worker paywall. ?demo=1 returns the TOC and an excerpt, unpaid. Costs 3 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations present, the description carries the full disclosure burden and does well: it states the exact cost (3 USDC on Base per successful call), the payment mechanism (x402), and the failure mode (returns the 402 challenge when no payment key is supplied). It does not describe the size or structure of the paid guide, but the essential cost/auth contract is clear.

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?

Four short sentences, front-loaded with the purpose, then the free-demo path, then the price and the failure mode. The second sentence ('Concise guide from Forge Agent Hub's own Worker paywall') partly repeats the first, but nothing is bloat.

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 no-parameter tool with no output schema, the definition covers what it returns, what it costs, how to preview it free, and what happens without payment. The one gap is the ambiguity of ?demo=1 against an empty parameter schema, which could trip up an agent trying to actually use it.

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. The mention of ?demo=1 adds useful semantics about a free-content mode, although it is mildly confusing that this appears to be a query flag on a tool with an empty input schema, leaving the agent unsure whether to pass it.

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 concrete resource (a playbook for becoming an x402 seller on Cloudflare Workers) and states its provenance (Forge Agent Hub's own Worker paywall), so the agent knows it returns guidance content rather than performing an action. It lacks an explicit verb like 'fetch' or 'return the playbook', which keeps it just short of a 5.

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 gives practical invocation guidance — use ?demo=1 for a free TOC and excerpt, expect a 402 challenge without a payment key — which is enough to steer a first call. It does not compare itself to any sibling (e.g. playbook_mcp_publish) or state when a full paid call is warranted over the free excerpt.

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