Skip to main content
Glama

Finding the first funder

address_first_funder
Read-onlyIdempotent

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.

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": {
      "request": "<request>"
    },
    "name": "address_first_funder"
  }
}

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.4/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, open-world, non-destructive lookup, so the safety profile is covered. The description adds beyond that: the funder is resolved across all chains so no chain argument is needed, and it enumerates the returned fields. It does not say what happens when no funder exists or when the wallet is fresh, which is the remaining behavioral gap.

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 sentences, no filler, and the core capability is front-loaded before the usage rationale. Every clause carries actionable information.

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?

An output schema exists, so return values need not be documented, and the description still summarizes them usefully. The tool is a single-parameter cross-chain lookup, and the description covers what it does and why it matters; only edge-case behavior (no funder found, non-EVM input) is left unaddressed.

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 description coverage is 100%, so the baseline would be 3. The description earns above baseline by explaining why there is no chain parameter — the funder is resolved across all chains — which is information an agent cannot derive from the schema itself and prevents it from inventing a chain filter.

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?

"Get the first address that ever funded an EVM wallet, with the funding transaction hash, chain and timestamp" names a specific verb and resource and pins down the exact record returned. The scope (earliest funder, cross-chain) makes it distinguishable from broader siblings like address_counterparties or address_related_addresses without opening any schema.

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 concrete when-to-use rationale: attributing an unlabelled wallet to a known entity, with the domain insight that first funders are often CEX withdrawals or owner-controlled wallets. It stops short of naming an alternative tool for cases where the first funder is unhelpful (e.g. multi-hop tracing), so no exclusions are stated.

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