x402-alpha

alpha_risk

Token safety assessment — audit status, rug pull signals, liquidity depth, holder concentration, honeypot detection, plus X and Reddit scam-report corroboration. $0.062 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_risk"
  }
}

Input Schema

Name	Required	Description
`chain`	No	Chain for lookup (auto-detect if omitted)
`symbol`	No	Token symbol (e.g., WIF)
`address`	No	Token contract address (preferred for accuracy)

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses payment cost ($0.062 USDC) and that payment is consumed even on timeouts, which is important behavioral context. However, it does not mention what happens if required parameters are missing (auto-detect fails?), rate limits, or other failure modes.

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 sentences with no wasted words. The first sentence front-loads the purpose and key features, the second adds essential cost and execution behavior. Every sentence earns its place.

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, the description should clarify what the tool returns (format, structure) but does not. It covers purpose, features, and cost but omits return value details and error handling. Adequate but with clear gaps.

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?

Input schema coverage is 100%, with each parameter described (chain, symbol, address). The description adds no further meaning to these parameters beyond what the schema provides, so a 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?

The description clearly states the tool's purpose: token safety assessment. It lists specific aspects like audit status, rug pull signals, liquidity depth, holder concentration, honeypot detection, and social corroboration, providing a precise verb-resource pair ('assess token safety'). This distinguishes it from sibling tools focused on other areas (e.g., alpha_news, alpha_sentiment).

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 implicitly indicates use for token risk evaluation but provides no explicit guidance on when to choose this tool over siblings (e.g., alpha_deep for deeper analysis, alpha_token for general info). It does not specify prerequisites or when not to use it.

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?