Skip to main content
Glama

EmblemAI AgentWallet

nansen-wallets: nansen_wallet_related_wallets

nansen_wallet_related_wallets
Read-onlyIdempotent

Wallets linked to an address (funded by, funded, deployed by, multisig signer, etc.) plus who first funded it. Use to cluster wallets owned by the same person or to trace insiders. 2 credits.

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": {
      "wallet_address": "<wallet_address>"
    },
    "name": "nansen_wallet_related_wallets"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination (default 1)
chainNoethereum, solana or robinhood. Default: solana for base58 addresses, ethereum for 0x addresses. For a 0x wallet call again with robinhood to cover Robinhood Chain.
limitNoRows to return (1-100, default 20)
wallet_addressYesWallet address (0x... for Ethereum/Robinhood, base58 for Solana)
include_first_funderNoAlso look up the first funder (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description's main addition is the cost disclosure ('2 credits'), which is genuinely useful for an agent budgeting calls. It says nothing about result shape, pagination limits, or whether the first-funder lookup is an extra upstream call.

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?

Two short sentences: the first front-loads what is returned with illustrative relationship types, the second gives the use case, and the credit cost is tacked on without padding. Nothing is wasted or buried.

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 five fully documented parameters, rich annotations, and no output schema, the description covers enough for correct invocation. The remaining gap is behavioral rather than structural — no hint about result volume or what the relationship records look like.

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 five parameters including chain defaults and the include_first_funder flag are already documented in structured form. The description only echoes the first-funder concept, adding no syntax or behavioral detail beyond the schema.

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 a concrete resource (wallets linked to an address) and enumerates the relationship types returned — funded by, funded, deployed by, multisig signer — plus the first-funder field. That level of specificity distinguishes it from generic lookups, though it never names a sibling like nansen_wallet_counterparties to sharpen the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two concrete use cases: clustering wallets owned by the same person, and tracing insiders. That is clear positive guidance, but there is no when-not condition and no mention of which sibling tool to prefer for related-but-different 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