Skip to main content
Glama

helius_get_epoch_schedule

Retrieve the Solana epoch schedule, specifying commitment level for confirmed or finalized data.

Instructions

Get the epoch schedule

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commitmentNo

Implementation Reference

  • src/tools.ts:231-240 (registration)
    Registration of the 'helius_get_epoch_schedule' tool with its name, description, and input schema. Imported from handlers/helius.ts.
    {
      name: "helius_get_epoch_schedule",
      description: "Get the epoch schedule",
      inputSchema: {
        type: "object",
        properties: {
          commitment: { type: "string", enum: ["confirmed", "finalized", "processed"] }
        },
        required: []
      }
  • Handler function getEpochScheduleHandler that calls connection.getEpochSchedule() to fetch epoch schedule data and returns it as a formatted string.
    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)}`);
      }
    }
  • Type definition GetEpochScheduleInput with optional commitment parameter.
    export type GetEpochScheduleInput = {
      commitment?: "confirmed" | "finalized" | "processed";
    }
  • Import statement for getEpochScheduleHandler from ./handlers/helius.js.
    getEpochScheduleHandler,
  • Import of GetEpochScheduleInput type from helius.types.
    GetEpochScheduleInput,
Behavior1/5

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

No annotations are present to indicate safety or side effects, and the description does not disclose any behavioral traits. The agent has no information about potential rate limits, permissions, or side effects.

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

Conciseness2/5

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

The description is only one sentence, which is under-specified. It is not concise in a helpful way; it lacks necessary detail.

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?

With no output schema and minimal description, the tool definition is completely inadequate. The agent cannot determine what data is returned or how to interpret results.

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 coverage is 0%, and the description does not explain the 'commitment' parameter's meaning or usage. The agent must rely solely on the enum values in the schema, which is insufficient for proper selection.

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

Purpose3/5

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

The description 'Get the epoch schedule' states a verb and resource, but is vague and does not distinguish from the sibling tool 'helius_get_epoch_info'. It lacks specificity about what an epoch schedule entails.

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 is provided. The description gives no context about prerequisites, typical use cases, 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/dcSpark/mcp-server-helius'

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