boo-x402-mcp

by lucle87

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

Token supply info

token_supply

Retrieve total supply, circulating supply, and decimals for any token by providing its contract address and chain.

Instructions

Total supply, circulating supply and decimals for a token.

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>",
      "chain": "<chain>"
    },
    "name": "token_supply"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	Chain: eth, bnb, base, solana.
`token`	Yes	Token contract address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 11, 2026

TDQS

B3.3/5.0

Behavior3/5

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

The description mentions it is a paid tool with a specific cost, which is helpful. However, no annotations are provided, and the description lacks details on data freshness, caching, or whether it is read-only. The cost disclosure adds some transparency but more context is needed.

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 concise with only two sentences, front-loading the core functionality and then adding the cost information. No wasted words.

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 covers the purpose and cost but lacks details about the return format (e.g., key names, units). With no output schema, the agent needs more context on what the response contains. Adequate but not comprehensive.

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%, so the schema defines both parameters sufficiently. The description does not add extra meaning beyond what the schema provides, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states what the tool provides: total supply, circulating supply, and decimals. It distinguishes from siblings like token_price and token_holders by specifying supply-related data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives such as token_snapshot or token_momentum. The description only explains what it does, not when it is appropriate.

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