Skip to main content
Glama
Sign In
zandronum-mcp

zandronum-mcp

by rc4l
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

List savegames

list_saves

Extract savegame metadata from .zds files: list title, map, engine, game wad, and creation time directly from PNG text chunks, without launching Zandronum.

Instructions

List .zds savegames in the save directory with metadata (title, map, engine, game wad, creation time) read from each save's PNG text chunks. No running game needed.

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

Input Schema

NameRequiredDescriptionDefault
dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description discloses that it reads metadata from PNG text chunks and doesn't require a running game. It doesn't mention if it modifies anything (likely not) or what happens if the directory doesn't exist. Moderate transparency.

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 sentence that efficiently conveys the tool's purpose, scope, and key constraint. No wasted words.

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

Completeness3/5

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

The description covers the main functionality and condition, but doesn't specify the output format (e.g., list of files vs. metadata), and the parameter is underspecified. Given the simplicity of the tool, it's adequate but not fully complete.

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?

The only parameter 'dir' has no schema description (0% coverage). The description mentions 'save directory' but doesn't explicitly state that 'dir' allows specifying a custom directory path or that it's optional. Some context is provided but not enough for an agent to understand the parameter's role.

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?

The description clearly states it lists .zds savegames with metadata from PNG text chunks, and specifies no running game needed. This is a specific verb+resource combination that distinguishes from sibling tools like load_game or save_game.

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 description says 'No running game needed,' indicating a key usage context. However, it doesn't provide when-not-to-use guidance or mention alternatives among the many sibling tools, which is a gap given the large sibling list.

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