Skip to main content
Glama

helius_get_epoch_info

Retrieve current Solana blockchain epoch details including slot information and block production data to monitor network status and timing.

Instructions

Get information about the current epoch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commitmentNo

Implementation Reference

  • The main handler function that executes the tool logic by calling the Helius RPC connection.getEpochInfo method with the provided commitment level and returns the epoch information.
    export const getEpochInfoHandler = async (input: GetEpochInfoInput): Promise<ToolResultSchema> => {
      try {
        const epochInfo = await (helius as any as Helius).connection.getEpochInfo(input.commitment);
        return createSuccessResponse(`Epoch info: ${JSON.stringify(epochInfo, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting epoch info: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The tool schema definition including name, description, and input schema for the helius_get_epoch_info tool.
    {
      name: "helius_get_epoch_info",
      description: "Get information about the current epoch",
      inputSchema: {
        type: "object",
        properties: {
          commitment: { type: "string", enum: ["confirmed", "finalized", "processed"] }
        },
        required: []
      }
    },
  • src/tools.ts:566-566 (registration)
    Registration of the 'helius_get_epoch_info' tool mapping its name to the getEpochInfoHandler function in the handlers dictionary.
    "helius_get_epoch_info": getEpochInfoHandler,
  • TypeScript type definition for the input parameters of the getEpochInfoHandler.
    export type GetEpochInfoInput = {
      commitment?: "confirmed" | "finalized" | "processed";
    }
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. It states it's a read operation ('Get'), but doesn't cover aspects like rate limits, authentication needs, error conditions, or what specific epoch information is returned. This is inadequate for a tool with potential complexity in blockchain contexts.

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 with no wasted words. It's front-loaded with the core purpose and appropriately sized for a simple-sounding tool, though this conciseness comes at the cost of completeness.

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?

For a blockchain tool with one parameter (even if optional) and no output schema, the description is insufficient. It doesn't explain what 'epoch information' includes, how the commitment parameter works, or what format the response takes. Given the technical domain and lack of structured documentation, more context is needed.

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

Parameters2/5

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

The description doesn't mention the 'commitment' parameter at all, despite it being the only parameter in the schema. With 0% schema description coverage, the description fails to compensate by explaining what 'commitment' means, its enum values, or how it affects the epoch information retrieval.

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 the resource 'information about the current epoch', which is specific and unambiguous. It distinguishes from siblings like 'helius_get_epoch_schedule' by focusing on current epoch info rather than schedule details, though it doesn't explicitly mention this differentiation.

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. The description doesn't mention prerequisites, context, or comparisons to sibling tools like 'helius_get_epoch_schedule', leaving the agent to infer usage based on 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