Skip to main content
Glama
Systems Manager

Systems Manager

Get Service Status

sm_service_get_service_status
Read-onlyIdempotent

Retrieve the status of a named system service to monitor availability and troubleshoot issues.

Instructions

Get service status (sm_service_operations). Operations for managing system services

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_service_get_service_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
service_nameNoName of the service

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.11

TDQS

C2.5/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 elsewhere. The description adds nothing beyond that — no note on scope (single service vs all), no return-shape hint, no indication that a null service_name might enumerate everything or fail.

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, but the second sentence is pure filler that restates the general domain rather than the tool's behavior. The useful fragment ("Get service status") is front-loaded, so it is not harmful, just padded.

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?

For a tool whose only parameter is optional, the definition should clarify the no-argument behavior and roughly what status fields come back; with no output schema, the description is the only place that could say so. Neither is addressed, leaving a real ambiguity for the agent.

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

Parameters3/5

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

Schema description coverage is 100% and there is only one optional parameter ("Name of the service"), so the schema already carries the semantics. The description never mentions service_name or its optionality, so it adds nothing beyond the schema — baseline 3 applies.

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?

"Get service status" does name a specific verb and resource, but the parenthetical "(sm_service_operations)" and the trailing "Operations for managing system services" add no discriminating information. Against siblings like sm_service_list_services or sm_service_start_service, the agent gets a rough idea of the read path but no crisp statement of what status data is returned.

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: nothing distinguishes this from sm_service_list_services, and nothing says whether to call it before start/stop/restart. It also doesn't tell the agent what happens if service_name is omitted, which is the key decision for a single optional parameter.

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