Skip to main content
Glama

helius_get_version

Retrieve the version of the Solana node to verify software status and compatibility.

Instructions

Get the version of the Solana node

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'helius_get_version' tool logic. It calls connection.getVersion() on the Helius SDK and returns the Solana node version as a success response, or an error response on failure.
    export const getVersionHandler = async (input: GetVersionInput): Promise<ToolResultSchema> => {
      try {
        const version = await (helius as any as Helius).connection.getVersion();
        return createSuccessResponse(`Version: ${JSON.stringify(version, null, 2)}`);
      } catch (error) {
        return createErrorResponse(`Error getting version: ${error instanceof Error ? error.message : String(error)}`);
      }
    }
  • The input type definition for the getVersionHandler. It is an empty object (GetVersionInput = {}) because no input parameters are needed.
    export type GetVersionInput = {}
  • src/tools.ts:266-272 (registration)
    The tool definition/registration in the tools array. Defines name 'helius_get_version', description 'Get the version of the Solana node', and an empty input schema (no required params).
    name: "helius_get_version",
    description: "Get the version of the Solana node",
    inputSchema: {
      type: "object",
      properties: {},
      required: []
    }
  • src/tools.ts:570-570 (registration)
    The handler mapping in the handlers dictionary, mapping the tool name 'helius_get_version' to the getVersionHandler function imported from the handlers module.
    "helius_get_version": getVersionHandler,
  • The createSuccessResponse helper used by the handler to format successful responses.
    export const createSuccessResponse = (message: string): ToolResultSchema => {
      return {
        content: [{
          type: "text",
          text: message
        }],
        isError: false
Behavior3/5

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

No annotations provided; description is minimal but accurate for a read-only operation. Does not specify return format or behavior, which is acceptable for a simple tool but could be improved.

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?

Single sentence, 8 words, with no wasted text; highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description is adequate for a tool with no parameters and no output schema; states purpose clearly. Slight improvement could mention return value type, but not necessary for basic understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so description adds no parameter info; baseline for zero parameters is 4 as schema coverage is 100%.

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

Purpose5/5

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

Description clearly states verb 'Get' and resource 'version of the Solana node', distinct from sibling tools that focus on balances, assets, or transactions.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool versus alternatives; usage is implied by its simple retrieval nature but lacks exclusions or context.

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