x402-alpha

alpha_search

Neural web search + Twitter + AI synthesis (Exa + Grok). $0.03 USDC. 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_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	Search query for crypto intelligence

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The description discloses the cost ($0.03 USDC) and that payment is consumed even on timeout, which are critical behavioral traits. However, no mention of success format, error behavior, or rate limits. With no annotations, the description partially covers transparency but lacks completeness.

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?

The description is two concise sentences. The first explains what the tool does, and the second covers critical cost information. No unnecessary words, and front-loaded with purpose.

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?

Given no output schema and no annotations, the description should compensate by explaining return format. It mentions synthesis but not what is returned (text, URLs, etc.). The cost warning adds value, but overall completeness is average for a simple tool with one parameter.

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?

The description does not add parameter-specific details beyond the input schema. Schema coverage is 100% (one param with description), so the baseline is 3. The tool name and description imply the query is for crypto, but no examples or format guidance are given.

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?

The description clearly states it is a neural web search combined with Twitter and AI synthesis using Exa and Grok. It distinguishes itself from sibling tools (e.g., alpha_memecoin) which are more specialized, making the general search purpose evident.

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?

No explicit when-to-use or when-not-to-use guidance is provided. However, the name 'alpha_search' and the context of specialized sibling tools imply it is for general crypto intelligence queries. Lack of explicit alternatives or exclusions keeps this at implied usage.

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?