Skip to main content
Glama

Web Scraper Markdown Reader, Live Search & Agent Pass x402 MCP

Mint 30-Day Prepaid Agent Bearer Pass ($4.90 USDC via x402)

buy_30day_agent_pass_x402
Read-onlyIdempotent

Mints a 30-day ak_x402_... Bearer pass unlocking all 5 Edge Gateways without per-call signatures ($4.90 USDC on Base via x402).

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

Input Schema

NameRequiredDescriptionDefault
agent_idNoAgent identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior1/5

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

The description says the tool "Mints" a pass and charges "$4.90 USDC on Base via x402", which is a state-changing, money-spending operation, while annotations declare readOnlyHint=true and destructiveHint=false. That is a direct conflict on the most consequential behavioral property an agent needs. With the annotation actively pointing the wrong way, the description should have made the payment/credential-issuance semantics unambiguous instead of leaving the agent to reconcile them.

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?

A single sentence with the cost, rail, and unlocked scope packed into one parenthetical, front-loaded on the verb. No filler, no redundancy with the title.

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

Completeness2/5

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

For a paid credential-minting tool with no output schema, the description omits critical operational facts: what the caller receives (the pass string, expiry, how to use it), whether repeat purchases stack or renew, whether the 0.90 USDC charge is refunded on failure, and how payment authorization happens. Combined with the readOnlyHint conflict, an agent cannot safely reason about cost or side effects before calling.

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% for the single agent_id parameter, so the schema already carries the semantics and baseline 3 applies. The description adds nothing about agent_id — not whether it defaults, whether it must match an existing agent, or what happens if omitted (the parameter is not required).

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 verb ("Mints"), a specific resource ("30-day ak_x402_... Bearer pass"), the exact scope it unlocks ("all 5 Edge Gateways"), and the payment rail/price. That is far more than a restatement of the title. It does not explicitly contrast itself with the per-call sibling tools (scrape_webpage_markdown_x402, search_live_web_x402), so it falls 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?

Usage is only implied: "without per-call signatures" hints that this is the right choice for high-volume, multi-gateway work, but the description never says so directly. There is no explicit statement of when to prefer this over the pay-per-call x402 siblings, nor any prerequisite (e.g. wallet balance, Base network, existing pass).

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.