Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_token_indicators

nansen_token_indicators
Read-onlyIdempotent

Nansen Score indicators for a token: risk indicators and reward indicators, each with score, signal, percentile and last trigger time. Good for a quick bullish/bearish/risk read. 5 credits.

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

Input Schema

NameRequiredDescriptionDefault
chainYes
token_addressYesToken contract address (use nansen_search to resolve a symbol first)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive behavior, so the bar is lower; the description adds return-field structure (score, signal, percentile, last trigger time) and a cost signal ('5 credits'), which is real behavioral context an annotations block cannot express. It omits any note on chain-specific coverage or empty/error results, keeping it out of 5 territory.

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?

Three short sentences, front-loaded with what the tool returns, then the use case, then cost. Every sentence carries information an agent would otherwise have to discover by calling the tool.

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?

With only two required parameters and no output schema, the description needs to describe the return shape, and it does so concretely (score/signal/percentile/trigger time for both risk and reward indicators). What is missing is minor: no explanation of what a Nansen Score actually measures or its range, which would help interpret the output.

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 50%: token_address carries its own description with a resolve-first hint, and chain is a self-documenting enum. The description adds nothing about either parameter, so it neither compensates for the gap nor introduces confusion. Baseline 3 fits when the schema largely speaks for itself.

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 verb-phrase ('Nansen Score indicators for a token') and enumerates the two indicator families (risk and reward), which separates it from sibling data tools like nansen_token_flows or nansen_token_ohlcv. It does not explicitly name a sibling it is not, so it stops short of a 5.

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?

'Good for a quick bullish/bearish/risk read' implies a use context but gives no explicit when-not guidance, no prerequisites, and no pointer to alternatives such as nansen_token_info for descriptive metadata. The agent must infer when this is the right tool rather than, say, the screener.

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