Skip to main content
Glama

nansen: nansen_smart_money_flows

nansen_smart_money_flows
Read-onlyIdempotent

Monitor net token flows from smart money addresses. Shows accumulation or distribution by funds and whales across chains.

Instructions

Get net token flows from smart money addresses. Shows accumulation/distribution by funds and whales.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chainYesChain to query
per_pageNoResults per page
Behavior3/5

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

Annotations already indicate readOnly, non-destructive, idempotent, and open world traits. The description adds context about accumulation/distribution by funds and whales but does not detail behavior beyond what annotations convey. No contradiction with annotations.

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 extremely concise: two sentences with no unnecessary words. It is front-loaded with the core action and immediately provides useful context.

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?

For a simple tool with two parameters and comprehensive annotations, the description is minimally adequate. However, it lacks details on return format, time period, or pagination behavior, which could be helpful for an agent.

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?

Input schema has 100% description coverage, so the schema already explains both parameters. The tool description adds no additional meaning beyond what the schema provides, meeting the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves net token flows from smart money addresses and shows accumulation/distribution, using a specific verb and resource. It distinguishes from sibling tools like nansen_smart_money_holdings and nansen_smart_money_trades by focusing on flows.

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?

The description provides no guidance on when to use this tool versus its siblings or alternatives. No explicit when-to-use, when-not-to-use, or exclusions are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/EmblemCompany/Agent-skills'

If you have feedback or need assistance with the MCP directory API, please join our Discord server