Skip to main content
Glama

helius_get_recent_performance_samples

Retrieve recent performance samples from the Solana blockchain to monitor network health and analyze transaction metrics.

Instructions

Get recent performance samples

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

Implementation Reference

  • The handler function that executes the tool logic: calls Helius RPC getRecentPerformanceSamples with optional limit, stringifies the result or returns error.
    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)}`);
      }
    }
  • MCP tool definition with name, description, and inputSchema (optional limit: number).
    {
      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)
    Registers the tool name to the getRecentPerformanceSamplesHandler in the handlers dictionary.
    "helius_get_recent_performance_samples": getRecentPerformanceSamplesHandler,
  • TypeScript type for the handler input, matching the JSON schema.
    export type GetRecentPerformanceSamplesInput = {
      limit?: number;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Get') without details on permissions, rate limits, data format, or whether it's a read-only or mutating operation. For a tool with no annotation coverage, this is insufficient to inform an agent about its behavior beyond the basic action.

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, efficient sentence with no wasted words. It is front-loaded and appropriately sized for the minimal information it conveys, making it easy to parse quickly.

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 no annotations, no output schema, and low parameter coverage, the description is incomplete. It does not explain what 'performance samples' entail, how results are returned, or any behavioral traits, leaving significant gaps for an AI agent to understand and use the tool effectively in context with its siblings.

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 input schema has one parameter ('limit') with 0% description coverage, and the tool description does not mention parameters at all. With low schema coverage, the description fails to compensate by explaining what 'limit' means (e.g., number of samples, time range). This leaves the parameter undocumented and adds no value beyond the schema.

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 recent performance samples' states a verb ('Get') and resource ('recent performance samples'), providing a basic purpose. However, it lacks specificity about what 'performance samples' are (e.g., system metrics, transaction data) and does not differentiate from sibling tools like 'helius_get_epoch_info' or 'helius_get_priority_fee_estimate', which might also retrieve performance-related data. This makes it vague but not tautological.

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 does not mention context, prerequisites, or exclusions, and with many sibling tools for data retrieval (e.g., 'helius_get_account_info', 'helius_get_asset'), there is no indication of when 'recent performance samples' is the appropriate choice. This leaves usage unclear.

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