Skip to main content
Glama
AgenSysAdmin

AgenSysAdmin

by E13ctr0N

check_services

Read-only

Check systemd service status on a remote Linux server via SSH; specify service names or omit them to view all running services.

Instructions

Check systemd service status. Pass specific service names or omit for all running services.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "server": "<server>"
    },
    "name": "check_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverYes
servicesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered structurally. The description adds one genuine behavioral detail beyond them: omitting the services argument returns all running services, which defines scope. It does not disclose whether privileged access is needed or what a status record contains.

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?

Two short sentences, front-loaded with the purpose followed by argument handling, with no filler. It is efficient, though so terse that brevity shades into under-specification for the required parameter.

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?

The tool is low complexity with only two parameters and no output schema, so expectations are modest. Even so, the required 'server' argument is completely unaddressed, and with no output schema the agent gets no hint about the shape of the returned status data.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the full burden. It explains the optional 'services' argument (list of names, default = all running), but the required 'server' parameter is never mentioned at all — not its format, identity source, or whether it must come from list_servers. Half the parameters remain opaque.

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

Purpose4/5

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

States a specific verb and resource: 'Check systemd service status.' An agent can tell this is a read-only status inspection, distinct from mutating siblings like manage_service. It stops short of naming that alternative, so the differentiation is implicit rather than explicit.

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

Usage Guidelines3/5

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

The second sentence gives practical invocation guidance (pass names, or omit for all running services), which is useful. However, it offers no when-to-use versus when-not guidance relative to siblings such as manage_service or system_info, so choosing this tool is left to inference from the name.

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