Skip to main content
Glama
nucleusv

Linux MCP daemon

by nucleusv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

cpu/list

Read-onlyIdempotent

List all logical CPUs by reading /proc/cpuinfo, returning vendor, model, speed and cache details per processor as text or structured JSON.

Instructions

Lists the machine's CPUs from /proc/cpuinfo. Read-only. Text output shows the number of logical processors and, for the FIRST processor only, vendor, model name, MHz (or BogoMIPS) and cache size. output_format: json (also yaml/table/wide) returns an array with one object per logical CPU using /proc/cpuinfo's own field names, which differ by architecture (x86 model name, cpu MHz, flags; ARM CPU implementer). It does not report sockets, cores or threads separately, and topology_only has no effect. For current load use cpu/load-average, for per-process CPU processes/top, for OS and kernel system/os-release.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
output_formatNoUse json for structured output (yaml, table and wide return the same JSON); default is text
topology_onlyNoHas no effect: accepted but ignored, the output is the same

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.4.1
    • changedInput schema / properties / output_format / description
      Previous value: -"Desired output format (e.g. json, yaml, table, wide). Defaults to text"New value: +"Use json for structured output (yaml, table and wide return the same JSON); default is text"
    • changedInput schema / properties / topology_only / description
      Previous value: -"Only return basic core topology"New value: +"Has no effect: accepted but ignored, the output is the same"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial context beyond them: text output only details the FIRST processor, json returns one object per logical CPU with architecture-dependent field names, and it explicitly discloses that it does not report sockets/cores/threads and that topology_only is inert.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose and read-only status, and each sentence carries distinct information (output shape, architecture caveats, sibling routing). It is dense and slightly long, but nothing is filler.

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?

With no output schema, the description carries the return-value burden and does so: it explains both the text and JSON output shapes plus the architecture-dependent field names. Nothing needed to call it correctly is missing.

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?

Schema coverage is 100% so the baseline is 3, but the description adds meaning beyond it: output_format json/yaml/table/wide all return the same JSON array, and field names vary by architecture (x86 vs ARM). It restates topology_only's no-op, which is already in the schema.

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?

States a specific verb and resource ('Lists the machine's CPUs from /proc/cpuinfo') and immediately differentiates itself from cpu/load-average, processes/top and system/os-release. An agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent to alternatives with the selecting condition: 'For current load use cpu/load-average, for per-process CPU processes/top, for OS and kernel system/os-release.' Both when-to-use and when-not-to-use are covered.

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

Deploy Server

Other Tools