Skip to main content
Glama

helius_get_recent_performance_samples

Retrieve recent performance samples from the Solana blockchain to analyze network throughput and validator efficiency.

Instructions

Get recent performance samples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • Handler function that calls connection.getRecentPerformanceSamples(input.limit) and returns the result as a JSON string.
    export const getRecentPerformanceSamplesHandler = async (input: GetRecentPerformanceSamplesInput): Promise<ToolResultSchema> => {
      try {
        const samples = await (helius as any as Helius).connection.getRecentPerformanceSamples(input.limit);
        return createSuccessResponse(`Recent performance samples: ${JSON.stringify(samples, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting performance samples: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • Input type definition for GetRecentPerformanceSamples, with an optional limit property.
    export type GetRecentPerformanceSamplesInput = {
      limit?: number;
    }
  • src/tools.ts:254-264 (registration)
    Tool registration in the tools array: name, description, and inputSchema with optional limit.
    {
      name: "helius_get_recent_performance_samples",
      description: "Get recent performance samples",
      inputSchema: {
        type: "object",
        properties: {
          limit: { type: "number" }
        },
        required: []
      }
    },
  • src/tools.ts:569-569 (registration)
    Handler mapping in the handlers dictionary connecting the tool name to getRecentPerformanceSamplesHandler.
    "helius_get_recent_performance_samples": getRecentPerformanceSamplesHandler,
  • Import of GetRecentPerformanceSamplesInput from helius.types.ts, used by the handler.
    } from "./helius.types.js";
    import { PublicKey, Commitment, VersionedMessage, LAMPORTS_PER_SOL } from "@solana/web3.js";
    import { ToolResultSchema } from "../types.js";
    import { createErrorResponse, createSuccessResponse, validatePublicKey } from "./utils.js";
Behavior2/5

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

Without annotations, the description carries the full burden of behavioral disclosure, but it only reiterates the tool's name. It fails to mention any side effects, data freshness, rate limits, or access requirements.

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?

The description is extremely concise (one short sentence), but it lacks any structural elements like bullet points or sections. It earns its place but does not provide enough information.

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?

Given the simplicity of the tool (1 optional param, no output schema), the description is incomplete. It does not explain what 'performance samples' are, the return format, or the impact of the 'limit' parameter.

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 schema has one optional parameter 'limit' with no description, and the tool description provides no additional meaning. With 0% schema description coverage, the description should compensate, but it does not explain how 'limit' affects results.

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 it retrieves recent performance samples, which distinguishes it from sibling tools that focus on accounts, assets, or transactions. However, it does not elaborate on what constitutes a 'performance sample,' leaving some ambiguity.

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 vs. alternatives. The sibling tools cover various blockchain data endpoints, but the description does not specify scenarios for performance samples versus other getter tools.

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