QuickBuild token-saver tools + x402

Base token batch (10 tokens + DEX price)

base_token_batch

Read-only

[PAID $0.01 USDC per call via x402 on Base; errors are free] Batch version of /api/base/token for Base mainnet (chain 8453): pass up to 10 comma-separated contract addresses in addresses and get, per token, contract/EOA check, ERC-20 name/symbol/decimals/totalSupply, proxy implementation, owner() and renounced flag, well-known flag, and market from DexScreener (USD price, total liquidity, 24h volume/change, FDV, top pair; market=0 to skip). A bad token yields a per-item error instead of failing the call. Fixed $0.01 per call (vs $0.002 x 10). Metadata cached 1 h, market 60 s. Defaults to USDC, WETH, AERO. Invalid input = 400, never charged.

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

Input Schema

Name	Required	Description	Default
`market`	No	Include DexScreener price/liquidity (default true).
`addresses`	No	Comma-separated Base token addresses (max 10). Optional: defaults to USDC, WETH, AERO.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond annotations: x402 payment model ($0.01 per call, errors free, invalid input = 400 and never charged), per-item error isolation on bad tokens, and cache TTLs (metadata 1 h, market 60 s). This is exactly the operational detail an agent needs before spending money on a call.

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?

Dense and front-loaded, with the payment note first and the core batching contract next. Slightly overloaded with parenthetical asides and prices, but nearly every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, yet the description enumerates the per-token return fields (contract check, ERC-20 metadata, proxy, owner/renounced, well-known flag, market price/liquidity/volume/FDV/top pair). Combined with error and caching behavior, an agent knows exactly what comes back and when to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3, but the description still adds meaning: the 10-address cap, comma-separated format, the default address set, and what 'market=0' disables. It reinforces rather than duplicates the schema.

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?

States a specific verb and resource ('Batch version of /api/base/token'), the chain (Base mainnet, 8453), and the exact cap (up to 10 comma-separated addresses). This clearly separates it from the single-token sibling base_token_info without needing the schema.

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

Usage Guidelines4/5

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

Gives concrete selection context: use this for batching (fixed $0.01 vs $0.002 x 10), set market=0 to skip DexScreener, and omit addresses to get USDC/WETH/AERO defaults. It doesn't explicitly say 'use base_token_info for a single token', so routing to the single-token sibling is left implicit.

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

All QuickBuild token-saver tools + x402 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?