Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_token_info

nansen_token_info
Read-onlyIdempotent

Token overview: name, socials, deployment date, market cap, FDV, supply, holder count, liquidity, and buy/sell volume, trade counts and unique buyers/sellers over a timeframe. 1 credit.

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": {
      "chain": "<chain>",
      "token_address": "<token_address>"
    },
    "name": "nansen_token_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYes
timeframeNoWindow for trading metrics (default 1d)
token_addressYesToken contract address (use nansen_search to resolve a symbol first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral information with the credit cost ('1 credit'), which matters for budgeting. It says nothing about data freshness, whether the timeframe affects only the trading fields, or failure behavior on unknown addresses.

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?

One dense sentence front-loads the resource and lists the returned fields, with the credit cost appended as a separate short clause. Every element carries information; the only mild cost is that the field list is a long comma run rather than grouped.

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?

With no output schema, enumerating the returned fields is the right move and is done well. However, for a token-analytics tool with three parameters and a timeframe enum, the description never explains how the timeframe interacts with the output or what an agent should expect across chains (ethereum vs solana vs robinhood).

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 67% and the two enriched parameters already document the timeframe default and the symbol-resolution step for token_address. The description contributes only the framing 'over a timeframe', which correctly signals that the trading metrics — not the static fields — are windowed. The chain parameter receives no explanation in either place.

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 resource and enumerates exactly what the overview contains (name, socials, deployment date, market cap, FDV, supply, holders, liquidity, trading metrics), so an agent knows the payload shape. It does not name or contrast with sibling token tools such as nansen_token_holders or nansen_token_dex_trades, so differentiation is only implied by the word 'overview'.

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?

There is no when-to-use guidance and no stated alternative — nothing says to use this for a broad snapshot and reach for nansen_token_holders or nansen_token_dex_trades for depth. The only routing hint ('use nansen_search to resolve a symbol first') lives in the schema, not the description.

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.

Resources