Skip to main content
Glama

helius_get_signatures_for_address

Retrieve transaction signatures for a Solana address. Use optional parameters to filter by limit, before, until, and commitment.

Instructions

Get transaction signatures for a Solana address

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYes
limitNo
beforeNo
untilNo
commitmentNo

Implementation Reference

  • Type definition for the tool's input: address (required), optional limit, before, until, and commitment.
    export type GetSignaturesForAddressInput = {
      address: string;
      limit?: number;
      before?: string;
      until?: string;
      commitment?: "confirmed" | "finalized" | "processed";
    }
  • src/tools.ts:15-15 (registration)
    Import of getSignaturesForAddressHandler from handlers.
    getSignaturesForAddressHandler,
  • src/tools.ts:162-176 (registration)
    Tool registration with name, description, and JSON Schema inputSchema defining address (required), limit, before, until, commitment.
    {
      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)
    Maps the tool name to the handler in the handler map.
    "helius_get_signatures_for_address": getSignaturesForAddressHandler,
  • Handler function that validates the public key, builds options (limit, before, until, commitment), calls helius.connection.getSignaturesForAddress(), and returns the signatures.
    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)}`);
      }
    }
Behavior2/5

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

Despite no annotations, the description provides no behavioral details such as pagination, rate limits, or response format, missing the opportunity to disclose key traits beyond the minimal 'get signatures'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise, but overly minimal; lacks structured details like parameter list or use cases, sacrificing informativeness for brevity.

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 5 parameters, no output schema, and no annotations, the description is severely incomplete, omitting return values, pagination, and parameter semantics.

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?

With 0% schema description coverage, the description fails to explain any of the 5 parameters (address, limit, before, until, commitment), adding no value beyond parameter names.

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?

Description clearly states the verb 'Get' and resource 'transaction signatures' scoped to a Solana address, distinguishing it from sibling tools like helius_get_signatures_for_asset.

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 on when to use this tool versus alternatives, no exclusions or prerequisites mentioned, leaving the agent to infer usage from the name alone.

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