Skip to main content
Glama

helius_get_leader_schedule

Retrieve the leader schedule for a specific epoch on Solana. Specify an optional slot and commitment level to filter results.

Instructions

Get the leader schedule for an epoch

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotNo
commitmentNo

Implementation Reference

  • The main handler function for the helius_get_leader_schedule tool. Calls connection.getLeaderSchedule() and returns the leader schedule for an epoch as a JSON string. Note: the slot and commitment input parameters are defined in the schema but not actually used in the handler.
    export const getLeaderScheduleHandler = async (input: GetLeaderScheduleInput): Promise<ToolResultSchema> => {
      try {
        // getLeaderSchedule doesn't accept parameters in the real SDK
        const leaderSchedule = await (helius as any as Helius).connection.getLeaderSchedule();
        return createSuccessResponse(`Leader schedule: ${JSON.stringify(leaderSchedule, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting leader schedule: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • TypeScript type definition for GetLeaderScheduleInput with optional slot (number) and commitment fields.
    export type GetLeaderScheduleInput = {
      slot?: number;
      commitment?: "confirmed" | "finalized" | "processed";
    }
  • src/tools.ts:242-252 (registration)
    Tool registration entry: defines the tool name 'helius_get_leader_schedule', description, and input JSON schema (slot and commitment properties).
    {
      name: "helius_get_leader_schedule",
      description: "Get the leader schedule for an epoch",
      inputSchema: {
        type: "object",
        properties: {
          slot: { type: "number" },
          commitment: { type: "string", enum: ["confirmed", "finalized", "processed"] }
        },
        required: []
      }
  • src/tools.ts:568-568 (registration)
    Handler mapping: maps the tool name 'helius_get_leader_schedule' to the getLeaderScheduleHandler function.
    "helius_get_leader_schedule": getLeaderScheduleHandler,
  • Import statement for getLeaderScheduleHandler from the handlers module.
    getLeaderScheduleHandler,
Behavior2/5

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

No annotations are provided, and the description lacks behavioral details such as read-only nature, rate limits, or response format. The one-sentence description does not disclose important traits.

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, but its extreme brevity results in under-specification rather than conciseness. Important information is missing.

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 lack of annotations and output schema, the description fails to provide essential context about output, behavior, or relationship between slot and epoch. It is insufficient for correct tool use.

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%, and the description does not explain the `slot` or `commitment` parameters. Without compensation, it leaves the agent uninformed about parameter semantics.

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 retrieves the leader schedule for an epoch, with a specific verb and resource. However, it does not distinguish from sibling tools like `helius_get_epoch_info` or `helius_get_epoch_schedule`, which could be confused. The mention of 'epoch' conflicts slightly with the `slot` parameter.

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. With many sibling `get` tools, the description provides no 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