Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

List PM2 Processes

listPM2Processes
Read-only

Lists PM2 processes on the Uptime Kuma host with name, ID, and status so you can identify a service for PM2 monitor configuration.

Instructions

Lists the PM2 processes on the Uptime Kuma host with their name, ID and status. A pm2 monitor names one, by name or ID, in typeFields.system_service_name. Fails if PM2 is not installed where Uptime Kuma runs (it isn't in Uptime Kuma's Docker image).

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": "listPM2Processes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
countYes
processesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful context beyond that: a hard failure condition when PM2 is not installed, including the notable case that it is absent from Uptime Kuma's Docker image. Return formatting is left to the output schema, which is reasonable.

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?

Three short sentences with no filler: what it returns comes first, the consumer (pm2 monitor) second, and the failure mode last. Every sentence carries information an agent can act on.

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

Completeness5/5

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

With an output schema covering return values, annotations covering safety, and no parameters, the description only needs to explain scope and failure behavior, and it does both. Nothing an agent needs to call this correctly appears to be missing.

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 no parameters, so there is nothing for the description to disambiguate beyond confirming the call is argument-free. The baseline for a zero-parameter tool applies.

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

Purpose5/5

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

States a specific verb and resource ('Lists the PM2 processes') plus the scope ('on the Uptime Kuma host') and the fields returned (name, ID, status). This is clearly distinguishable from the many other list* siblings, which cover different resources (Docker hosts, monitors, tags).

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?

It gives concrete usage context: a pm2 monitor references one of these entries via typeFields.system_service_name, telling the agent why it would call this tool. It does not spell out explicit alternatives or when-not-to-call, but the intended context is clear.

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