Skip to main content
Glama

Nansen

by io.github.nansen-ai
OverviewDiscussionsAdmin

Finding the first funder

address_first_funder
Read-only

Get the first address that ever funded an EVM wallet, with the funding transaction hash, chain and timestamp. Use this to attribute an unlabelled wallet to a known entity — the first funder is often a CEX withdrawal or a wallet the same owner already controls. The funder is resolved across all chains, so no chain argument is needed.

Input Schema

NameRequiredDescriptionDefault
requestYesRequest for the first address that funded a wallet (flattened).

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "description": "Request for the first address that funded a wallet (flattened).",
-    "properties": {
-      "address": {
-        "description": "EVM address to look up the first funder for",
-        "type": "string"
-      }
-    },
-    "required": [
-      "address"
-    ],
-    "type": "object"
-  }
-]
    • addedInput schema / properties / request / description
      Added value: +"Request for the first address that funded a wallet (flattened)."
    • addedInput schema / properties / request / properties
      Added value: +{
+  "address": {
+    "description": "EVM address to look up the first funder for",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / request / required
      Added value: +[
+  "address"
+]
    • addedInput schema / properties / request / type
      Added value: +"object"
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already establish read-only, non-destructive, open-world behavior, and the description adds useful operational context: the funder is resolved across all chains, so no chain argument is needed. It does not discuss auth, rate limits, or edge cases, but it meaningfully supplements the structured safety hints.

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 two tight sentences: the first states exactly what is returned, and the second explains the key use case and cross-chain behavior. It is front-loaded and has no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only lookup with annotations and an output schema, the description supplies the essential purpose, usage rationale, and cross-chain resolution behavior. Nothing critical is missing for an agent to select and invoke it correctly.

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 100% for the single nested address parameter, so the schema already documents the input. The description adds useful meaning by clarifying that the address is an EVM wallet and that chain resolution is automatic, explaining why no chain parameter exists.

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 states a precise verb and resource: get the first address that ever funded an EVM wallet, plus the funding transaction hash, chain, and timestamp. The 'first funder' scope is clearly distinct from sibling tools such as address_counterparties, address_related_addresses, and address_transactions.

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 a clear use case: attributing an unlabelled wallet to a known entity because the first funder is often a CEX withdrawal or another wallet controlled by the same owner. It does not explicitly name when not to use it or compare against all plausible alternatives, so it falls short of a 5.

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

All Nansen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources