Skip to main content
Glama

Nansen Wallet Profiler

nansen_wallet_profiler
Read-onlyIdempotent

Labels & profile for wallet X, returns Nansen labels (e.g. "Smart Money", "Fund", exchange/entity tags) for a wallet address, plus a best-effort USD balance summary. Example: nansen_wallet_profiler({ address: "0x28c6c06298d514db089934071355e5743bf21d60", chain: "ethereum", _apiKey: "your-nansen-key" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "ethereum",
      "_apiKey": "your-nansen-api-key",
      "address": "0x28c6c06298d514db089934071355e5743bf21d60"
    },
    "name": "nansen_wallet_profiler"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain the address lives on (default "ethereum"); use "all" to span chains where supported.
_apiKeyYesNansen API key from your nansen.ai account (paid, $10/10k credits PAYG).
addressYesWallet address to profile (required), e.g. "0x28c6...d60".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Nansen API key from your nansen.ai account (paid — $10/10k credits PAYG)."New value: +"Nansen API key from your nansen.ai account (paid, $10/10k credits PAYG)."
  2. First observed

TDQS

A3.5/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 real value with the "best-effort USD balance summary" caveat, warning the agent that balance figures may be incomplete; however it says nothing about credit cost, rate limits, or what happens for unlabeled or unknown addresses.

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?

The primary statement is front-loaded and readable, and the label examples clarify the return value. The trailing example call largely duplicates the schema's examples block, which is mild redundancy but not harmful.

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 three-parameter read-only tool with no output schema and strong annotations, the description covers the resource, the returned label categories, and a reliability caveat on balances. Minor gaps remain around multichain behavior with chain="all" and results for wallets Nansen has not labeled.

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 100%, so all three parameters are already documented, including the "all" chain option and API key pricing. The description's inline example reinforces address and chain usage but adds no semantics the schema lacks, so the baseline 3 applies.

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 states a specific resource (a wallet address) and a specific output (Nansen labels such as "Smart Money", "Fund", exchange/entity tags, plus a USD balance summary). It never names an alternative tool, so an agent cannot tell from the text alone why it would pick this over nansen_smart_money_holdings or nansen_smart_money_netflow.

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 by the example call: profile a single address, optionally spanning chains. There is no explicit when-to-use statement, no when-not-to-use, and no pointer to a sibling for aggregate smart-money or flow queries.

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.