Skip to main content
Glama

get_transfers_for_owner

Retrieve NFT transfer history for a specific wallet address to track asset movements and ownership changes across ERC721 and ERC1155 tokens.

Instructions

Get NFT transfers for an owner

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerYesThe wallet address to get transfers for
pageKeyNoKey for pagination
fromBlockNoStarting block number for the query
toBlockNoEnding block number for the query
orderNoOrder of results (ascending or descending)
tokenTypeNoType of token (ERC721 or ERC1155)
contractAddressesNoList of contract addresses to filter by

Implementation Reference

  • index.ts:657-699 (registration)
    Registration of the 'get_transfers_for_owner' tool in the ListToolsRequestSchema handler, defining name, description, and input schema.
    {
      name: "get_transfers_for_owner",
      description: "Get NFT transfers for an owner",
      inputSchema: {
        type: "object",
        properties: {
          owner: {
            type: "string",
            description: "The wallet address to get transfers for",
          },
          pageKey: {
            type: "string",
            description: "Key for pagination",
          },
          fromBlock: {
            type: "number",
            description: "Starting block number for the query",
          },
          toBlock: {
            type: "number",
            description: "Ending block number for the query",
          },
          order: {
            type: "string",
            enum: ["asc", "desc"],
            description: "Order of results (ascending or descending)",
          },
          tokenType: {
            type: "string",
            enum: ["ERC721", "ERC1155"],
            description: "Type of token (ERC721 or ERC1155)",
          },
          contractAddresses: {
            type: "array",
            items: {
              type: "string",
            },
            description: "List of contract addresses to filter by",
          },
        },
        required: ["owner"],
      },
    },
  • TypeScript type definition for the tool's parameters, extending Alchemy SDK's GetTransfersForOwnerOptions with required owner field.
    type GetTransfersForOwnerParams = GetTransfersForOwnerOptions & {
      owner: string;
    };
  • Helper function to validate input parameters for the get_transfers_for_owner tool.
    const isValidGetTransfersForOwnerParams = (
      args: any
    ): args is GetTransfersForOwnerParams => {
      return (
        typeof args === "object" &&
        args !== null &&
        typeof args.owner === "string" &&
        (args.pageKey === undefined || typeof args.pageKey === "string") &&
        (args.fromBlock === undefined || typeof args.fromBlock === "number") &&
        (args.toBlock === undefined || typeof args.toBlock === "number") &&
        (args.order === undefined || typeof args.order === "string") &&
        (args.tokenType === undefined || typeof args.tokenType === "string") &&
        (args.contractAddresses === undefined ||
          Array.isArray(args.contractAddresses))
      );
    };
  • Import of Alchemy SDK type GetTransfersForOwnerOptions used for the tool schema.
    import type {
      GetNftsForOwnerOptions,
      GetNftMetadataOptions,
      AssetTransfersParams,
      GetNftSalesOptions,
      GetContractsForOwnerOptions,
      GetOwnersForNftOptions,
      GetTransfersForContractOptions,
      GetTransfersForOwnerOptions,
      TransactionReceiptsParams,
      GetTokensForOwnerOptions,
      GetBaseNftsForContractOptions,
    } from "alchemy-sdk";
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal information. It doesn't mention whether this is a read-only operation (implied by 'Get'), potential rate limits, authentication needs, pagination behavior beyond the 'pageKey' parameter, or what the output format looks like (e.g., list of transfers with details). The description is too brief to cover these aspects adequately.

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 a single, efficient sentence with zero waste—it directly states the tool's purpose without unnecessary words. It's appropriately sized for a straightforward query tool and front-loaded with the core action. Every word earns its place.

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

Completeness2/5

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

Given the complexity (7 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain the return values (e.g., transfer details like timestamps, token IDs), behavioral traits like pagination or rate limits, or how it integrates with sibling tools. For a tool with multiple filtering options and no structured output definition, more context is needed to guide effective use.

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 the schema already documents all 7 parameters thoroughly with descriptions and enums. The description adds no additional meaning beyond what's in the schema—it doesn't clarify parameter interactions, default values, or usage examples. This meets the baseline of 3 since the schema does the heavy lifting.

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 clearly states the verb ('Get') and resource ('NFT transfers for an owner'), making the purpose immediately understandable. It distinguishes from siblings like 'get_asset_transfers' (broader asset types) and 'get_transfers_for_contract' (different scope), though not explicitly. However, it lacks specificity about what 'transfers' entails (incoming, outgoing, or both).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't explain how it differs from 'get_asset_transfers' (which might include fungible tokens) or 'get_nfts_for_owner' (which might show current holdings rather than transfer history). The description offers no context about prerequisites, timing, or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/itsanishjain/alchemy-sdk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server