Skip to main content
Glama
mcp-uptime-kuma

mcp-uptime-kuma

List Games

listGames
Read-only

Look up the GameDig ID a game server monitor needs by game name or ID, since Uptime Kuma does not validate it on save. Returns matching IDs, names, default ports and notes.

Instructions

Finds the GameDig ID a gamedig (game server) monitor needs in its game field, by game name or ID, e.g. "minecraft", "counter strike 2", "valheim". Returns each match's ID, name, default port and notes. Uptime Kuma does not check the ID when the monitor is saved, so look it up rather than guess.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default: 20, up to 100)
searchNoPart of the game name or ID; matched loosely. Omit to list games from the start.

Output Schema

NameRequiredDescriptionDefault
countYesHow many games matched, of which `games` holds the first `limit`
gamesYes
totalYesHow many games GameDig supports

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, matching the description's read-only lookup framing. Beyond that, the description discloses the return fields (ID, name, default port, notes) and the important behavioral caveat that an invalid ID will silently be accepted at save time.

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?

Two sentences, front-loaded with the core purpose and followed by the return shape and the caution. No filler, and every clause carries information the agent needs.

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?

For a simple two-parameter read-only lookup with an output schema, the description covers purpose, return contents, and the operational pitfall. Nothing an agent needs in order to call it correctly is 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?

Schema coverage is 100%, so the baseline is 3; the description adds value by clarifying that `search` matches loosely against either name or ID and by supplying example query strings. It does not explain `limit` beyond the schema, which is acceptable since the schema already covers it.

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: finds the GameDig ID needed in a gamedig monitor's game field, looked up by game name or ID. The concrete examples ("minecraft", "counter strike 2", "valheim") make the resource unambiguous and distinguish it from generic list_* siblings.

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?

Gives an explicit usage condition and rationale: Uptime Kuma doesn't validate the ID on save, so look it up rather than guess. It doesn't name an alternative tool, but the guidance on when to call this versus guessing is clear and actionable.

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