Skip to main content
Glama

helius_get_signatures_for_address

Retrieve transaction signatures for a Solana address to track wallet activity, verify transactions, or analyze blockchain interactions.

Instructions

Get transaction signatures for a Solana address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
limitNo
beforeNo
untilNo
commitmentNo

Implementation Reference

  • The handler function getSignaturesForAddressHandler that validates the address and calls helius.connection.getSignaturesForAddress with optional parameters.
    export const getSignaturesForAddressHandler = async (input: GetSignaturesForAddressInput): Promise<ToolResultSchema> => {
      const addressResult = validatePublicKey(input.address);
      if (!(addressResult instanceof PublicKey)) {
        return addressResult;
      }
      
      try {
        const options: any = {};
        if (input.limit) options.limit = input.limit;
        if (input.before) options.before = input.before;
        if (input.until) options.until = input.until;
        if (input.commitment) options.commitment = input.commitment;
        
        const signatures = await (helius as any as Helius).connection.getSignaturesForAddress(addressResult, options);
        return createSuccessResponse(`Signatures: ${JSON.stringify(signatures, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting signatures: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • TypeScript type definition for the input parameters of the handler.
    export type GetSignaturesForAddressInput = {
      address: string;
      limit?: number;
      before?: string;
      until?: string;
      commitment?: "confirmed" | "finalized" | "processed";
    }
  • src/tools.ts:162-176 (registration)
    MCP tool registration including name, description, and input schema definition.
    {
      name: "helius_get_signatures_for_address",
      description: "Get transaction signatures for a Solana address",
      inputSchema: {
        type: "object",
        properties: {
          address: { type: "string" },
          limit: { type: "number" },
          before: { type: "string" },
          until: { type: "string" },
          commitment: { type: "string", enum: ["confirmed", "finalized", "processed"] }
        },
        required: ["address"]
      }
    },
  • src/tools.ts:562-562 (registration)
    Mapping of tool name to its handler function in the handlers dictionary.
    "helius_get_signatures_for_address": getSignaturesForAddressHandler,
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does ('Get transaction signatures') without any information on permissions, rate limits, response format, pagination, or error handling. This is inadequate for a tool with multiple parameters and no output schema.

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, clear sentence that efficiently conveys the core function without unnecessary words. It is front-loaded with the essential action and resource, making it easy to parse quickly.

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

Completeness1/5

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

Given the complexity (5 parameters, 0% schema coverage, no annotations, no output schema), the description is severely incomplete. It lacks details on parameter usage, behavioral traits, return values, and differentiation from siblings, making it insufficient for effective tool invocation in this context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning none of the 5 parameters (address, limit, before, until, commitment) are documented in the schema. The description adds no meaning beyond the tool's name, failing to explain what these parameters do, their formats, or how they affect the query. This leaves parameters like 'before' and 'until' ambiguous.

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 tool's purpose with a specific verb ('Get') and resource ('transaction signatures for a Solana address'), making it immediately understandable. However, it doesn't distinguish this tool from its sibling 'helius_get_signatures_for_asset', which suggests a similar function but for assets rather than addresses, leaving room for potential confusion.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'helius_get_transaction' or 'helius_get_account_info' that might overlap in use cases, the absence of explicit when-to-use or when-not-to-use instructions leaves the agent without context for selection.

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/dcSpark/mcp-server-helius'

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