Skip to main content
Glama

Finding related wallets

address_related_addresses
Read-onlyIdempotent

Get information about related addresses of an input address.

Note: This only includes the the "special" connections 'First Funder', 'Signer', 'Previous Signer', 'Multisig Signer of', 'Previous Multisig Signer of', 'Deployed via', 'Deployed by', 'Deployed Contract', 'Created Contract', 'Created by'. To get related wallets, also check address counterparties. First funder exchange withdrawal address does usually NOT belong to the same entity as the address, only deposit addresses. Only information is that it has been funded by the exchange.

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_related_addresses"
  }
}

Input Schema

NameRequiredDescriptionDefault
requestYesAddressRelatedAddressesRequest containing parameters and pagination settings

Output Schema

NameRequiredDescriptionDefault
rowsNo
chainsNoChains that were queried.
addressNo
messageNoNotice or error text when the tool returns no data rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / request / properties / chain / description
      Added value: +"Blockchain network to query. Use a specific chain to limit results or all for the supported networks."
  2. Changed5 schema fields changed
    • addedInput schema / properties / request / additionalProperties
      Added value: +false
    • removedInput schema / properties / request / anyOf
      Removed value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "description": "Complete request for address related addresses (flattened).",
      -    "properties": {
      -      "address": {
      -        "description": "Wallet address to analyze for related addresses",
      -        "type": "string"
      -      },
      -      "chain": {
      -        "default": "all",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "address"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedInput schema / properties / request / properties
      Added value: +{
      +  "address": {
      +    "description": "Wallet address to analyze for related addresses",
      +    "type": "string"
      +  },
      +  "chain": {
      +    "default": "all",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / request / required
      Added value: +[
      +  "address"
      +]
    • addedInput schema / properties / request / type
      Added value: +"object"
  3. Changed9 schema fields changed
    • addedOutput schema / description
      Added value: +"Structured result of `address_related_addresses`."
    • addedOutput schema / properties / address
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Address"
      +}
    • addedOutput schema / properties / chains
      Added value: +{
      +  "description": "Chains that were queried.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "title": "Chains",
      +  "type": "array"
      +}
    • addedOutput schema / properties / message
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Notice or error text when the tool returns no data rows.",
      +  "title": "Message"
      +}
    • removedOutput schema / properties / result
      Removed value: -{
      -  "type": "string"
      -}
    • addedOutput schema / properties / rows
      Added value: +{
      +  "items": {
      +    "description": "One address connected to the queried address.",
      +    "properties": {
      +      "address": {
      +        "title": "Address",
      +        "type": "string"
      +      },
      +      "address_label": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Address Label"
      +      },
      +      "block_timestamp": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Block Timestamp"
      +      },
      +      "chain": {
      +        "title": "Chain",
      +        "type": "string"
      +      },
      +      "relation": {
      +        "description": "How the address is connected, e.g. First Funder, Signer, Deployed by.",
      +        "title": "Relation",
      +        "type": "string"
      +      },
      +      "transaction_hash": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "default": null,
      +        "title": "Transaction Hash"
      +      }
      +    },
      +    "required": [
      +      "address",
      +      "chain",
      +      "relation"
      +    ],
      +    "title": "RelatedAddressRow",
      +    "type": "object"
      +  },
      +  "title": "Rows",
      +  "type": "array"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "result"
      -]
    • addedOutput schema / title
      Added value: +"AddressRelatedAddressesOutput"
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  4. Changed1 schema field changed
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "description": "Complete request for address related addresses (flattened).",
      -    "properties": {
      -      "addresses": {
      -        "description": "List of wallet addresses to analyze for related addresses",
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "chain": {
      -        "default": "all",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "addresses"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "description": "Complete request for address related addresses (flattened).",
      +    "properties": {
      +      "address": {
      +        "description": "Wallet address to analyze for related addresses",
      +        "type": "string"
      +      },
      +      "chain": {
      +        "default": "all",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "address"
      +    ],
      +    "type": "object"
      +  }
      +]
  5. Changed4 schema fields changed
    • removedInput schema / $defs
      Removed value: -{
      -  "AddressRelatedAddressesRequest": {
      -    "description": "Complete request for address related addresses (flattened).",
      -    "properties": {
      -      "addresses": {
      -        "description": "List of wallet addresses to analyze for related addresses",
      -        "items": {
      -          "type": "string"
      -        },
      -        "type": "array"
      -      },
      -      "chain": {
      -        "default": "all",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "addresses"
      -    ],
      -    "type": "object"
      -  }
      -}
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / request / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "type": "object"
      -  },
      -  {
      -    "$ref": "#/$defs/AddressRelatedAddressesRequest"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": true,
      +    "type": "object"
      +  },
      +  {
      +    "description": "Complete request for address related addresses (flattened).",
      +    "properties": {
      +      "addresses": {
      +        "description": "List of wallet addresses to analyze for related addresses",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "chain": {
      +        "default": "all",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "addresses"
      +    ],
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / request / description
      Added value: +"AddressRelatedAddressesRequest containing parameters and pagination settings"
  6. First observed

TDQS

A4.1/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 description focuses on scope: a closed list of relation types that are excluded/included, plus an interpretive caveat about exchange funding. It does not discuss result volume or pagination, but adds real analytical context beyond the annotations.

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?

Front-loads the purpose, then two short sentences of caveats that each carry information an agent would otherwise get wrong. Minor waste in the duplicated 'the the' typo and the slightly bureaucratic enumeration of relation types.

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 no explanation. Between the relation-type list, the sibling pointer, and the entity-attribution caveat, the definition covers what an agent needs to call and correctly interpret this read-only analytical tool.

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% with a single nested request object (address plus an optional chain defaulting to 'all'), so the schema already carries parameter meaning. The description only refers to an 'input address' and adds nothing about the chain parameter.

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?

States a specific verb and resource ('Get information about related addresses of an input address') and then enumerates exactly which connection types are included, which lets an agent distinguish this from the separately named address_counterparties sibling.

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?

Explicitly points the agent to address counterparties for a fuller 'related wallets' picture, and warns that first-funder exchange withdrawal addresses usually do not belong to the same entity. No explicit when-not-to-use case, but the routing guidance is concrete.

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