Skip to main content
Glama
Systems Manager

Systems Manager

Get Uptime

sm_system_get_uptime
Read-onlyIdempotent

Retrieves system uptime to monitor host availability and identify unexpected reboots or stability issues.

Instructions

Get uptime (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_uptime"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.8/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 fully covered by structured data. The description adds nothing beyond that — it does not say whether uptime is measured since boot or since an agent session, nor whether the call is cheap or rate-limited. Not contradictory, but purely redundant with 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.

Conciseness3/5

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

It is short and front-loads the operation name, which is good. However, the second sentence is filler about the broader operations family that does not help an agent decide or invoke anything, so not every sentence earns its place.

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 zero-argument read tool with full annotation coverage, the definition is minimally sufficient to invoke. The remaining gap is the absence of any output shape hint (seconds vs. formatted string, since-boot vs. boot timestamp) and there is no output schema to compensate, leaving the agent to discover the return format at call time.

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 no parameter meaning for the description to convey and the baseline of 4 applies. Nothing in the description misleads about inputs.

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 verb+resource pair "Get uptime" is specific enough to identify the operation, but the description never clarifies what kind of uptime (system since-boot vs. a service or process) or what unit it returns. The parenthetical "(sm_system_operations)" and the trailing sentence about packages, health, and updates describe the tool family, not this tool, so they add no distinguishing power against siblings such as sm_system_get_hardware_statistics or sm_service_get_service_status.

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, no precondition, and no mention of any alternative tool. The second sentence reads as group taxonomy ("System operations for managing packages, system health, and updates") rather than instruction for selecting this tool over a host record or OS statistics call.

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