Skip to main content
Glama

token_intel

Read-onlyIdempotent

Lightweight token lookup: price, market cap, volume, and basic risk assessment for any EVM or Solana token. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": {
      "address": "<address>"
    },
    "name": "token_intel"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoBlockchain networkethereum
addressYesToken contract address or name

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base",
      -  "arbitrum",
      -  "optimism",
      -  "polygon",
      -  "bsc",
      -  "avalanche",
      -  "linea",
      -  "unichain",
      -  "sonic",
      -  "solana"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "arbitrum",
      +  "optimism",
      +  "polygon",
      +  "bsc",
      +  "avalanche",
      +  "linea",
      +  "unichain",
      +  "sonic",
      +  "hyperevm",
      +  "solana"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
      -  "ethereum",
      -  "base",
      -  "solana",
      -  "polygon",
      -  "arbitrum"
      -]New value: +[
      +  "ethereum",
      +  "base",
      +  "arbitrum",
      +  "optimism",
      +  "polygon",
      +  "bsc",
      +  "avalanche",
      +  "linea",
      +  "unichain",
      +  "sonic",
      +  "solana"
      +]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the description only needs to add traits beyond that. It does: a hard free quota of 10 calls per day and the notable behavior that once exceeded, the tool returns a pay-per-call x402 endpoint and price instead of results. That non-obvious fallback is exactly the kind of disclosure an agent needs before deciding to call it.

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 sentences, zero waste, and front-loaded with the capability before the quota caveat. Nothing is repeated from the schema or annotations.

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

Completeness4/5

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

For a two-parameter read-only lookup with no output schema, this covers capability, chain scope, and the quota/payment fallback. The remaining gap is what 'basic risk assessment' actually contains and how an unresolvable address or unsupported chain is reported, but the core decision-relevant information is present.

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 coverage is 100%: both address and chain (with a full enum and a default of ethereum) are already documented in the schema. The description adds 'any EVM or Solana token', which reinforces the chain scope but contributes no format, naming, or disambiguation detail beyond what the schema supplies. Baseline 3 applies.

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?

States a specific verb and resource ('Lightweight token lookup') and enumerates the returned data: price, market cap, volume, and basic risk assessment. The word 'lightweight' plus 'basic risk assessment' implicitly separates it from deeper siblings like token_risk_metrics, token_research, and token_compare, though none are named explicitly.

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?

Usage is implied by the free-tier framing: this is the cheap first-pass lookup, and heavier analysis lives elsewhere. It never states when to prefer token_risk_metrics, token_research, or solana_token_risk_scan, nor what to do when the tool stops returning data after the quota is exhausted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.