x402-alpha

alpha_deep

Deep multi-source research (Exa + Firecrawl + Claude + up to 99 tweets). $0.10 USDC. May take up to 60s. Payment is consumed on execution, including timeouts.

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": {
      "query": "<query>"
    },
    "name": "alpha_deep"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Research query (e.g., "Solana DeFi trends", "Base L2 ecosystem", token name)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses multi-source usage, cost, timeout, and that payment is consumed on execution including timeouts. Could mention output format or error handling but is sufficiently transparent for a single-parameter tool.

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?

Single sentence with no wasted words. Key elements (multi-source, cost, timeout, payment consumption) are front-loaded and clearly communicated.

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?

Given the complexity (multi-source, cost, timeout, single param), the description covers the essential behavioral aspects. Missing details on output format or timeout behavior (e.g., what happens on timeout) but adequate for the tool's simplicity.

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% with example queries. The tool description does not add additional parameter information beyond the schema, so baseline score of 3 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?

Clearly states it is a deep multi-source research tool listing specific sources (Exa, Firecrawl, Claude, tweets), cost, and timeout. Distinguishes from sibling tools like alpha_brief or alpha_search by emphasizing depth and multiple sources.

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?

Provides clear context: it is for deep research, costs $0.10 USDC, and may take up to 60s. Does not explicitly state when not to use it or name alternatives among siblings, but the depth/time/cost imply it is for thorough investigations.

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

All x402-alpha 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?