Skip to main content
Glama

helius_get_epoch_schedule

Retrieve the epoch schedule for Solana blockchain to understand timing and slot distribution across epochs.

Instructions

Get the epoch schedule

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commitmentNo

Implementation Reference

  • The core handler function that executes the tool logic by calling getEpochSchedule on the Helius Solana connection and formatting the response.
    export const getEpochScheduleHandler = async (input: GetEpochScheduleInput): Promise<ToolResultSchema> => {
      try {
        // getEpochSchedule doesn't accept any parameters in the real SDK
        const epochSchedule = await (helius as any as Helius).connection.getEpochSchedule();
        return createSuccessResponse(`Epoch schedule: ${JSON.stringify(epochSchedule, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting epoch schedule: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The MCP tool schema defining the name, description, and input validation schema.
    {
      name: "helius_get_epoch_schedule",
      description: "Get the epoch schedule",
      inputSchema: {
        type: "object",
        properties: {
          commitment: { type: "string", enum: ["confirmed", "finalized", "processed"] }
        },
        required: []
      }
    },
  • src/tools.ts:567-567 (registration)
    Registration of the tool name to its handler function in the handlers dictionary.
    "helius_get_epoch_schedule": getEpochScheduleHandler,
  • TypeScript type definition for the handler input, matching the tool schema.
    export type GetEpochScheduleInput = {
      commitment?: "confirmed" | "finalized" | "processed";
    }
Behavior1/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 none. It does not indicate if this is a read-only operation, its performance characteristics, error conditions, or any side effects, failing to compensate for the lack of structured 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?

The description is extremely concise with a single sentence, 'Get the epoch schedule', which is front-loaded and wastes no words. However, this brevity borders on under-specification, as it lacks necessary detail for effective tool use.

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 tool's complexity (involving blockchain epoch data), no annotations, no output schema, and poor parameter documentation, the description is incomplete. It fails to explain what an epoch schedule is, how it's used, or what the tool returns, making it inadequate for agent understanding.

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?

The input schema has one parameter ('commitment') with 0% description coverage, and the tool description provides no information about parameters. This leaves the parameter's purpose, such as its role in fetching epoch data, completely undocumented, failing to compensate for the schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get the epoch schedule' restates the tool name with minimal elaboration, making it a tautology. It specifies the verb 'Get' and resource 'epoch schedule' but lacks detail on what an epoch schedule is or its significance, unlike clearer sibling tools like 'helius_get_balance' or 'helius_get_transaction' that imply more specific functions.

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

Usage Guidelines1/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 does not mention context, prerequisites, or comparisons to sibling tools such as 'helius_get_epoch_info', which might offer related epoch data, leaving the agent without usage direction.

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