Skip to main content
Glama

EmblemAI AgentWallet

nansen: nansen_chain_rank

nansen_chain_rank
Read-onlyIdempotent

Growth metrics for Ethereum, Solana and Robinhood Chain: transactions, active addresses, DEX volume, gas spend, revenue and TVL with % change over 7/30/365 days. 1 credit.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nansen_chain_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
time_frame_daysNoComparison window (default 7)

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 establish read-only, idempotent, open-world behavior, so the bar is lower, and the description still adds real value by disclosing the cost (1 credit) and by implying it returns data for all three chains rather than requiring a chain parameter. With no output schema, listing the exact metrics returned also serves as return-value disclosure. It stops short of describing response shape or ordering of ranked results.

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?

One front-loaded sentence delivers scope, metric list, time windows and cost with zero filler. Nothing is repeated or padded.

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 a zero-required-parameter, read-only aggregate tool this is nearly complete: scope, metrics, time windows and credit cost are all stated, which compensates for the absent output schema. What is missing is only the shape of the ranked comparison output and the currency/units of the monetary metrics.

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 100% and the single parameter has an enum with its own description, so the schema already does the work. The description restates the 7/30/365-day windows and echoes the default framing, which is mild reinforcement rather than added meaning — the baseline 3 for full coverage is appropriate.

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 names the resource (chain-level growth metrics for Ethereum, Solana and Robinhood Chain) and enumerates the concrete metrics returned — transactions, active addresses, DEX volume, gas spend, revenue, TVL. That is enough to distinguish it from wallet- and token-scoped siblings. It does not explicitly say it is a ranking/comparison tool despite the 'chain_rank' name, leaving a small ambiguity.

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?

Usage is only implied: an agent can infer this is the tool for chain-level growth comparisons rather than per-wallet or per-token analysis. There is no explicit when-to-use statement, no mention of prerequisites, and no named alternative for related chain-level questions.

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