x402-alpha

alpha_narrative

Detect and track active market narratives — AI tokens, RWA, L2, memecoins, DePIN. $0.05 USDC. Payment is consumed on execution, including timeouts.

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

Input Schema

Name	Required	Description
`limit`	No	Number of narratives to return (default: 5)
`query`	No	Free-text narrative query
`narrative`	No	Narrative slug (ai, rwa, meme, l2, depin, defi, gaming)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It only notes the payment and timeout behavior, omitting details such as side effects, rate limits, idempotency, or what happens on invalid input. The lack of output schema means return format is also not described.

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?

The description is two sentences long with no fluff. It front-loads the core purpose and then adds a cost note. It could be slightly more structured (e.g., separating purpose from cost), but it is concise.

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?

Given that the tool has three optional parameters and no output schema, the description falls short. It does not explain the return format, error handling, pagination, or other aspects essential for an agent to use it effectively.

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?

All three parameters are documented in the input schema with descriptions (100% coverage). The tool description adds no further semantic value beyond listing example narrative slugs, so it meets the baseline for high schema coverage.

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 'Detect and track active market narratives' and lists specific examples like AI tokens, RWA, L2, memecoins, DePIN. This verb+resource combination distinguishes it from sibling tools like alpha_memecoin or alpha_trending.

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?

The description mentions a cost of $0.05 USDC and that payment is consumed on execution including timeouts, but it does not provide explicit guidance on when to use this tool versus alternatives like alpha_search or alpha_sentiment.

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?