Skip to main content
Glama
Sign In

Tollkit Crypto

by io.github.UltraStarz
OverviewDiscussionsAdmin

Token info

token_info
Read-only

Look up a token on Base, Ethereum (ERC-20 contract) or Solana (SPL mint): name, symbol, decimals and total supply, plus mint and freeze authority on Solana, read live from the chain. Use it to confirm what an address actually is before acting on it.

$0.002 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You have a token address and need to know what it is before acting on it. Use instead: token_check for safety warnings and liquidity; token_price for its price. Parameters: token: ERC-20 contract or SPL mint. chain: base (default), ethereum or solana. Returns: name, symbol, decimals, total supply; on Solana, mint and freeze authority.

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_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNo"base" (default), "ethereum" or "solana".
tokenYesERC-20 contract, or SPL mint on Solana.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds material context beyond them: live on-chain reads, a $0.002 USDC x402 cost, that failed calls are free, and the quote-then-pay flow via omitting `payment`. That is exactly the kind of operational detail annotations cannot convey.

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?

Front-loaded with the core capability, then cleanly sectioned into cost, when-to-use, alternatives, parameters and returns. Minor redundancy: 'before acting on it' appears twice and the parameter/returns lines echo the schema, but overall it is tight and scannable.

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, and the description compensates by enumerating the returned fields, including the Solana-specific mint/freeze authority. Combined with cost and payment-flow disclosure, an agent has everything needed to call it correctly.

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 already documents all three parameters including the chain enum and the payment quote flow. The description's parameter section largely restates the schema ('ERC-20 contract or SPL mint', 'base (default)') without adding format or validation detail, so baseline 3 applies.

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 ('Look up a token') plus the exact fields returned (name, symbol, decimals, total supply, Solana authorities) and the supported chains. It explicitly distinguishes itself from token_check and token_price, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

Has an explicit 'When to use' condition (you have a token address and need to know what it is) and a 'Use instead' section naming both alternatives with their distinct purposes (safety/liquidity vs price). Nothing is left to inference.

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

All Tollkit Crypto toolsInspect
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