Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_flow_intelligence

nansen_flow_intelligence
Read-onlyIdempotent

Who is moving a token: net USD flow, average flow and wallet count for Smart Traders, whales, top-PnL traders, public figures, exchanges and fresh wallets over a timeframe. Exchange inflow = likely selling; fresh-wallet inflow can mean insiders. 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_flow_intelligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainYes
timeframeNoWindow (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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds genuinely useful non-annotation context: a concrete cost ('1 credit') and a heuristic for reading exchange versus fresh-wallet inflow. It says nothing about response shape, pagination, or how missing/small cohorts are represented.

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?

Two dense sentences, front-loaded with the core question and metric list before the interpretive tip and cost. No padding; the only slightly buried element is the credit cost appended at the end.

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 no output schema, the description carries the burden of describing returns, and it does so by naming the three metrics and the six cohort breakdowns. Combined with annotations covering side effects, what remains missing (chain parameter meaning, empty-cohort behavior) is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67% and the description reinforces the timeframe concept ('over a timeframe') and the token scoping, while the schema itself handles enum values, the 1d default and the nansen_search resolution hint. Chain selection is never mentioned in the description, leaving one real gap, but the agent still has enough to call it correctly.

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 opens with a concrete framing ('Who is moving a token') and enumerates the exact metrics (net USD flow, average flow, wallet count) and the wallet cohorts covered (Smart Traders, whales, top-PnL, public figures, exchanges, fresh wallets). It is clearly distinct in subject from generic siblings like token_flows or token_holders, though it never explicitly names an alternative.

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?

Use is implied by the cohort list and by interpretive hints ('Exchange inflow = likely selling; fresh-wallet inflow can mean insiders'), which tells the agent what question this answers. There is no explicit when-to-use versus when-to-prefer a sibling tool, and no stated prerequisite beyond resolving the token address.

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