Skip to main content
Glama
Sign In
arch-mcp-server

arch-mcp-server

by DankyoDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Unit status

svc_status
Read-onlyIdempotent

Inspect a systemd unit's status, PID, start time, restarts, memory, tasks, and last error before reading logs.

Instructions

State, main PID, start time, restarts, memory, tasks and last error of one systemd unit. Use it before reading logs.

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": {
      "unit": "<unit>"
    },
    "name": "svc_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitYesUnit name, e.g. nginx.service
detailNodetailed adds unit file state and fragment pathconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive behavior, so the bar is lower. The description adds genuine value beyond them by enumerating what the response contains (memory, tasks, last error), which matters because there is no output schema. It does not state what happens for an unknown or stopped unit, leaving a small gap.

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 sentences, front-loaded with the substance and ending on the actionable usage hint; nothing is redundant. The field list is dense but readable rather than padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description compensates by listing the returned fields, and the single required parameter is fully documented in the schema. Missing only error/edge-case behavior and any explicit sibling differentiation for a tool this simple.

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%, including the meaning of the detail enum ("detailed adds unit file state and fragment path"), so the schema already carries parameter semantics. The description adds nothing beyond it for unit or detail, which is the expected baseline 3.

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 names a specific resource (one systemd unit) and enumerates the concrete fields returned (state, main PID, start time, restarts, memory, tasks, last error), so an agent can distinguish it from siblings like svc_list or svc_failed without opening the schema. It stops short of an explicit contrast with those siblings, but the scope is unambiguous.

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

Usage Guidelines4/5

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

"Use it before reading logs" gives a concrete sequencing cue that routes the agent toward log_errors/log_query after this check. There is no explicit when-not guidance or mention of svc_failed/svc_list as alternatives, so it is clear context without full exclusions.

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