Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_token_flows

nansen_token_flows
Read-onlyIdempotent

Daily time series of a token's balance held by one holder group (Smart Money, whales, public figures, exchanges or top 100 holders): balance, USD value, holder count, inflows and outflows (DEX/CEX). Shows accumulation trends. 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_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLook-back window in days ending now (default 30). Ignored when date_from is set.
pageNoPage number for pagination (default 1)
chainYes
labelNoHolder group (default smart_money)
limitNoRows to return (1-100, default 30)
date_toNoExplicit end (YYYY-MM-DD or ISO 8601). Defaults to now.
date_fromNoExplicit start (YYYY-MM-DD or ISO 8601). Overrides days.
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?

The annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description still adds useful context beyond annotations: daily granularity, one-holder-group scope, the fields returned, and the 1-credit cost. It does not specify pagination behavior or auth requirements, but that is a minor gap given the annotation coverage.

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?

The description is front-loaded with the dataset definition, followed by the analytical use case and cost. Every sentence carries useful information: what is returned, what trend it supports, and the credit charge. There is no redundant or vague wording.

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 an 8-parameter tool with no output schema, the description does a good job enumerating the returned fields and time-series granularity. It does not detail the output row structure or pagination semantics, but those are reasonably covered by the schema and annotations for a read-only data tool.

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 88%, so the schema already explains most parameters, including date overrides, pagination, and the token address resolution hint. The description reinforces the holder-group concept by naming Smart Money, whales, public figures, exchanges, and top 100 holders, but it adds little syntax or format detail beyond the schema's enum and parameter descriptions.

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?

The description clearly states the resource and shape: a daily time series of a token's balance held by one holder group, including balance, USD value, holder count, and inflows/outflows. It distinguishes the data from raw token info or trades, but it does not explicitly contrast itself with the similar sibling nansen_smart_money_flows.

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?

The phrase 'Shows accumulation trends' implies an analytical use case for tracking holder-group positioning over time. However, it gives no explicit when-to-use or when-not-to-use guidance, and it does not route the agent toward or away from related tools such as nansen_smart_money_flows.

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