Skip to main content
Glama
arjshiv

Local Utilities MCP Server

by arjshiv

get_node_version

Returns the Node.js version of the environment running the MCP server. Use it to verify the runtime version.

Instructions

Returns the Node.js version information of the environment running the MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function 'registerNodeVersionTool' registers the 'get_node_version' tool on the MCP server. It defines the tool name, description, and async handler that returns Node.js version info as JSON.
    export function registerNodeVersionTool(server: McpServer): void {
      server.tool(
        "get_node_version",
        "Returns the Node.js version information of the environment running the MCP server.",
        async () => {
          // Error handling simplified, process.version/versions are generally safe
          const versionInfo = getNodeVersionInfo();
          return {
            content: [{
              type: "text",
              text: JSON.stringify(versionInfo, null, 2) // Keep JSON for structured data
            }]
          };
        }
      );
    } 
  • Interface INodeVersionInfo defines the return type: nodeVersion (string) and details (NodeJS.ProcessVersions).
    interface INodeVersionInfo {
      nodeVersion: string;
      details: NodeJS.ProcessVersions;
    }
  • The 'getNodeVersionInfo' helper function retrieves process.version and process.versions to build version information.
    export function getNodeVersionInfo(): INodeVersionInfo { // Export for testing
      return {
        nodeVersion: process.version,
        details: process.versions,
      };
    }
  • src/index.ts:7-7 (registration)
    Import statement for registerNodeVersionTool from the node-version module.
    import { registerNodeVersionTool } from "./mcp/node-version.js";
  • src/index.ts:22-22 (registration)
    The tool is registered by calling registerNodeVersionTool(server) in the main entry point.
    registerNodeVersionTool(server);
Behavior4/5

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

No annotations are provided, so the description alone must convey behavioral traits. The description indicates a read-only operation via 'Returns', which is sufficient for this simple retrieval tool. It does not mention side effects, but none are expected.

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 concise sentence that front-loads the purpose, with no extraneous words.

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

Completeness5/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 (no input parameters, no output schema, no complex behavior), the description covers all necessary context for an agent to understand and invoke it correctly.

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?

The input schema has zero parameters, so the baseline score is 4. No additional parameter description is needed.

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?

The description uses a clear verb 'Returns' and specifies the resource 'Node.js version information of the environment running the MCP server', which is distinct from sibling tools like get_hostname or get_public_ip.

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 usage guidelines or alternatives are given, but the purpose is self-explanatory: use it to get the Node.js version. For a simple tool, this implied usage is adequate.

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/arjshiv/localutils-mcp-server'

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