OpsChugex LocalOps MCP

Overview Schema Source Related Servers Discussions Admin

CPU Status

cpu_status

Read-onlyIdempotent

Samples CPU utilization over a set interval and returns processor metadata and load averages to check local host performance.

Instructions

Sample CPU utilization and return processor metadata and load averages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cpu_status"
  }
}

Input Schema

Name	Required	Description	Default
`sampleMs`	No

Output Schema

Name	Required	Description	Default
`model`	Yes
`speedMHz`	Yes
`loadAverage`	Yes
`logicalCores`	Yes
`usagePercent`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 2, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the tool samples utilization and returns metadata and load averages, but does not explain sampling duration, blocking behavior, or any auth/rate-limit context beyond the annotations.

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?

A single, front-loaded sentence with no wasted words. It is appropriately sized for a simple status tool.

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?

For a one-parameter tool with rich annotations and an output schema, the description covers the basic purpose adequately. However, it omits usage guidance and parameter semantics, leaving meaningful gaps for correct invocation.

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

Parameters1/5

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

There is one parameter (sampleMs) with 0% schema description coverage, and the description never mentions it or explains its effect on the sampling window. The description therefore fails to compensate for the schema coverage gap.

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 states a specific verb + resource (sample CPU utilization) and enumerates return content (processor metadata, load averages). It is clearly distinct from siblings like memory_status and disk_status, though it does not explicitly differentiate itself from broader tools such as system_info or system_health.

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?

No guidance is provided about when to use this tool versus alternatives. It implies a CPU-specific inspection context but gives no conditions, exclusions, or routing advice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.