boo-x402-mcp

Overview Schema Source Related Servers Discussions Admin

Token price & liquidity

token_price

Retrieve live token price, liquidity, 24h volume, FDV, and market cap from DEX pairs on eth, bnb, base, solana. Billed $0.01 USDC per call via x402.

Instructions

Live price, liquidity, 24h volume, FDV and market cap for a token from DEX pairs.

PAID TOOL: up to $0.01 USDC per call (x402 on Base). Paid automatically from your configured wallet.

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": {
      "token": "<token>"
    },
    "name": "token_price"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Optional chain hint: eth, bnb, base, solana.
`token`	Yes	Token contract / mint address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description bears full responsibility. It discloses the tool is paid (up to $0.01 USDC per call) and uses 'live' data from DEX pairs, but does not specify rate limits, error behavior (e.g., if token not found), or authentication requirements beyond wallet configuration.

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?

Two concise sentences: first explains outputs and source, second explains cost. No unnecessary words. Front-loaded with key purpose information.

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?

The description lists expected outputs (price, liquidity, volume, FDV, market cap) and source (DEX pairs), but lacks detail on output format, units, aggregation (single pair vs multiple), and fallback behavior. Given no output schema, more completeness is warranted.

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% (both 'chain' and 'token' are described). The description adds no additional meaning beyond what the schema provides; it only lists output fields, not parameter semantics. Baseline 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 provides 'Live price, liquidity, 24h volume, FDV and market cap' from DEX pairs. It uses specific verbs and resources ('price', 'liquidity', etc.), distinguishing it from sibling tools like token_supply or token_rugcheck.

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 implies usage for token price/liquidity data but does not provide explicit when-to-use or when-not-to-use guidance. No alternatives like other token info tools (e.g., token_momentum) are mentioned.

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