Skip to main content
Glama
JackXuyi

Current operating environment

getNodeInfo

Retrieve Node.js version details from the current operating environment to verify installations and check compatibility.

Instructions

获取当前设备安装的 Node.js 版本信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/index.ts:271-279 (registration)
    Tool registration in the listTools handler: defines name, description, and empty input schema for getNodeInfo.
    {
      name: "getNodeInfo",
      description: "获取当前设备安装的 Node.js 版本信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    }
  • Handler implementation for getNodeInfo tool: fetches Node.js version, npm version, global packages, and other runtime info using process object and execSync, returns JSON stringified response.
    case "getNodeInfo": {
      let nodeInfo = {};
      try {
        // 获取 Node.js 版本信息
        const nodeVersion = process.version;
        const nodeFullVersion = execSync('node --version').toString().trim();
        const npmVersion = execSync('npm --version').toString().trim();
        
        // 获取已安装的全局 npm 包
        const globalPackages = execSync('npm list -g --depth=0 --json').toString();
        const parsedGlobalPackages = JSON.parse(globalPackages);
        
        // 获取 Node.js 环境信息
        nodeInfo = {
          version: nodeVersion,
          fullVersion: nodeFullVersion,
          npmVersion: npmVersion,
          platform: process.platform,
          arch: process.arch,
          globalPackages: parsedGlobalPackages.dependencies || {},
          execPath: process.execPath,
          features: process.features,
          modules: process.versions
        };
      } catch (error) {
        // 出错时返回基本信息
        nodeInfo = {
          version: process.version,
          platform: process.platform,
          arch: process.arch
        };
      }
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(nodeInfo, null, 2)
        }]
      };
    }
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 states it 'gets' information, implying a read-only operation, but doesn't specify whether it requires permissions, returns structured data, has any side effects, or handles errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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, clear sentence in Chinese that directly states the tool's purpose without any extraneous information. It is front-loaded and efficiently communicates the core functionality, making it highly concise and well-structured.

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

Completeness3/5

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

Given the tool has no parameters, no annotations, and no output schema, the description is minimal but adequate for a simple read operation. It specifies what information is retrieved (Node.js version on the current device), which covers the basic purpose. However, it lacks details on output format, error handling, or usage context, which could be important for integration.

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 tool has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics, and it appropriately doesn't mention any. A baseline of 4 is applied since no parameters exist, and the description doesn't introduce unnecessary complexity.

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 action ('获取' meaning 'get') and the resource ('Node.js 版本信息' meaning 'Node.js version information'), making the purpose unambiguous. It specifies '当前设备安装的' (installed on the current device), which adds context, but it doesn't explicitly differentiate from potential siblings like getPlatformInfo or getHardwareInfo that might also provide system-level details.

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like getPlatformInfo or getHardwareInfo that might overlap in providing system information, there's no indication of when this specific tool is appropriate or what distinguishes it from others in the list.

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/JackXuyi/env-mcp'

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