Skip to main content
Glama
Systems Manager

Systems Manager

Get Os Statistics

sm_system_get_os_statistics
Read-onlyIdempotent

Retrieve operating system statistics to assess system health and guide package and update management.

Instructions

Get os 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_os_statistics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — in fact "System operations for managing packages, system health, and updates" describes a toolset category rather than this read-only call, and it never indicates what data comes back or how costly/fresh it is.

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?

The text is short and front-loaded, so nothing is buried. However, the second sentence does no work for this specific tool and reads as boilerplate copied from the parent category, so a portion of the content fails to 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?

This is a zero-argument read tool with no output schema, so the description is the only place an agent can learn what "os statistics" actually contains. It supplies none of that, leaving the return shape and the boundary against hardware/uptime/health-check siblings completely unspecified.

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 the baseline of 4 applies; there is no parameter meaning for the description to supply. The schema has no properties for the description to contradict.

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

Purpose2/5

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

"Get os statistics" merely restates the tool name and title, and the parenthetical "(sm_system_operations)" points at a group label rather than clarifying scope. With siblings like sm_system_get_hardware_statistics, sm_system_get_uptime, and sm_system_system_health_check, the description never says which statistics this returns or how it differs from those.

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 when-to-use guidance is given, and no alternative is named even though the sibling list contains several overlapping read tools. The agent must guess between this and sm_system_get_hardware_statistics or sm_system_system_health_check from names alone.

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