Skip to main content
Glama
Sign In
mcp-system

mcp-system

by MikeyBeez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

service_status

Check the status of a system service on macOS or Linux. Provide the service name to see if it is active, stopped, or in an error state.

Instructions

Check status of a system service (macOS/Linux)

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": {
      "service": "<service>"
    },
    "name": "service_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
serviceYesService name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states the action ('Check status') without explaining what a status check entails, whether privileged access is required, or what kind of output to expect.

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

Conciseness5/5

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

The description is a single, short sentence that is immediately clear and front-loaded. Every word earns its place, and there is no extraneous information.

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?

Given no output schema or annotations, the description leaves the agent without knowledge of the return format, possible statuses, or how to interpret the result. Even for a simple tool, the absence of behavioral context makes it incomplete for reliable invocation.

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 coverage is 100% because the single parameter 'service' is described as 'Service name'. The description adds slight context (system service, macOS/Linux) but does not go beyond the schema in explaining parameter values or format, so the baseline score of 3 applies.

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?

The description uses a specific verb 'Check' with a clear resource 'status of a system service' and includes platform scope (macOS/Linux). It is distinct from sibling tools like process_list, though it does not explicitly differentiate itself from similar status-related tools.

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 guidance is provided on when to use this tool versus alternatives such as system_info or process_list. There is no mention of exclusions, prerequisites, or context that would help an agent decide between options.

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