Skip to main content
Glama
JackXuyi

Current operating environment

getCpuInfo

Retrieve CPU information from the current operating environment to analyze system specifications and monitor performance metrics.

Instructions

获取当前系统的 CPU 信息

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation for the 'getCpuInfo' tool. It uses Node.js 'os.cpus()' to fetch CPU information and returns it as a JSON string in the tool response format.
    case "getCpuInfo": {
      const cpuInfo = {
        cpus: os.cpus()
      };
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify(cpuInfo, null, 2)
        }]
      };
    }
  • src/index.ts:46-53 (registration)
    Registration of the 'getCpuInfo' tool in the list of available tools. Defines the tool name, Chinese description, and an empty input schema (no parameters required).
    {
      name: "getCpuInfo",
      description: "获取当前系统的 CPU 信息",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
  • Input schema for the 'getCpuInfo' tool, specifying an empty object (no input parameters). Note: output schema is not explicitly defined.
    inputSchema: {
      type: "object",
      properties: {},
      required: []
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 the tool retrieves CPU information but doesn't specify what type of information (e.g., model, cores, speed), whether it requires permissions, if it's read-only or has side effects, or any rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 in Chinese: '获取当前系统的 CPU 信息' (get current system CPU information). It's front-loaded with the core purpose, has zero wasted words, and is appropriately sized for a simple tool. Every part of the sentence earns its place.

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 tool's complexity (simple read operation with no parameters) and the absence of annotations and output schema, the description is incomplete. It doesn't explain what CPU information is returned (e.g., details vs. summary), potential errors, or behavioral traits. For a tool with no structured output documentation, the description should provide more context about the return value.

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 the schema description coverage is 100% (since there are no parameters to describe). The description doesn't need to add parameter semantics beyond what the schema provides. A baseline score of 4 is appropriate as there are no parameters to document, and the description doesn't introduce any confusion.

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 tool's purpose as '获取当前系统的 CPU 信息' (get current system CPU information), which is a specific verb+resource combination. However, it doesn't explicitly distinguish itself from sibling tools like 'getCpuUsage' or 'getHardwareInfo', which might provide overlapping or related information. The purpose is clear but lacks sibling differentiation.

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 siblings like 'getCpuUsage' (which might focus on usage metrics) and 'getHardwareInfo' (which could include broader hardware details), there's no indication of context, exclusions, or when this specific CPU info tool is preferred. It relies solely on the tool name for implicit usage.

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