Skip to main content
Glama
JackXuyi

Current operating environment

getCpuUsage

Monitor CPU utilization in real-time to identify performance bottlenecks and optimize system resources for the current operating environment.

Instructions

获取当前平台的 CPU 占用率

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Schema definition for the getCpuUsage tool, including name, description, and empty input schema.
      name: "getCpuUsage",
      description: "获取当前平台的 CPU 占用率",
      inputSchema: {
        type: "object",
        properties: {},
        required: []
      }
    },
  • Handler implementation for getCpuUsage tool. Calculates overall CPU usage percentage by aggregating idle and total tick times from os.cpus().
    case "getCpuUsage": {
      const cpus = os.cpus();
      const totalIdle = cpus.reduce((acc, cpu) => acc + cpu.times.idle, 0);
      const totalTick = cpus.reduce((acc, cpu) => acc + Object.values(cpu.times).reduce((a, b) => a + b, 0), 0);
      const cpuUsage = 1 - totalIdle / totalTick;
    
      return {
        content: [{
          type: "text",
          text: JSON.stringify({ cpuUsage: (cpuUsage * 100).toFixed(2) + '%' }, 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 the tool 'gets' CPU usage, implying a read-only operation, but doesn't specify whether this requires permissions, how frequently it can be called, what format the output is in, or if it's real-time vs. averaged data. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that directly states the tool's function without any fluff or redundancy. It's front-loaded with the core purpose and appropriately sized for a simple, parameter-less tool, 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.

Completeness2/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but adequate for basic understanding. However, it lacks details on output format, error handling, or system-specific behaviors, which could be important for an AI agent to use it correctly in varied contexts. With no annotations or output schema, the description should provide more contextual completeness.

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). In such cases, the baseline score is 4, as the description doesn't need to compensate for any parameter documentation gaps. The description appropriately focuses on the tool's purpose without unnecessary parameter details.

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 verb ('获取' meaning 'get') and resource ('CPU 占用率' meaning 'CPU usage'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'getCpuInfo', which might provide related but different CPU information, leaving some ambiguity in 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 like 'getCpuInfo' or other system monitoring tools in the sibling list. It lacks context on use cases, prerequisites, or exclusions, offering only a basic functional statement without operational guidance.

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