Skip to main content
Glama
Systems Manager

Systems Manager

Get Hardware Statistics

sm_system_get_hardware_statistics
Read-onlyIdempotent

Retrieves hardware statistics to support system health checks, package management, and update planning.

Instructions

Get hardware statistics (sm_system_operations). System operations for managing packages, system health, and updates

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": "sm_system_get_hardware_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered without the description. The description adds no behavior beyond that — it does not indicate whether results are live or cached, what sections are returned, or how the open-world access manifests. The second sentence is generic server boilerplate rather than disclosure about this tool.

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

Conciseness3/5

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

It is short and front-loaded, which is good, but the second sentence about managing packages and updates is filler unrelated to a statistics read, and the "(sm_system_operations)" fragment is noise. Roughly half the text does not earn 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?

With no parameters and no output schema, the description is the only source of information about what the agent will actually receive, and it never enumerates the hardware metrics returned. For a tool sitting among many overlapping read-only system-metrics siblings, that omission is the single most important gap.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No parameter meaning is lost because none exists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb and resource ("Get hardware statistics"), but never says which statistics — CPU, memory, disk, thermal — leaving it ambiguous against siblings like sm_system_get_os_statistics, sm_disk_get_disk_usage, and sm_system_get_uptime. The parenthetical "(sm_system_operations)" and the second sentence about "managing packages, system health, and updates" describe the server group, not this tool, so they add no disambiguation.

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?

There is no when-to-use guidance at all: no statement of what distinguishes hardware statistics from OS statistics or the various disk/process siblings. The description is not misleading, but the agent must guess the selection context entirely from the name.

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