zandronum-mcp

by rc4l

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Load map

load_map

Load any map by its lump name (e.g., MAP01, E1M1) to switch the Zandronum engine to that level for testing or gameplay.

Instructions

Load a map by its lump name (e.g. MAP01, E1M1).

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": {
      "mapName": "<mapName>"
    },
    "name": "load_map"
  }
}

Input Schema

Name	Required	Description	Default
`mapName`	Yes
`instance`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 26, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations provided, and the description gives no behavioral details beyond 'load a map'. For a state-changing operation, it should disclose side effects (e.g., replaces current map), permission requirements, or state implications.

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?

Single sentence, directly to the point, no unnecessary words. Front-loaded with purpose.

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?

Adequate for a simple tool with no output schema, but missing context about side effects (e.g., overwrites current map) and the role of the 'instance' parameter.

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 0%. The description adds meaning for mapName via examples of lump names (MAP01, E1M1), but provides no explanation for the 'instance' parameter, leaving its purpose unclear.

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?

Clearly states the action (load), resource (map), and the key identifier (lump name) with examples (MAP01, E1M1). Distinguishes from sibling tools like load_game, which load saved games rather than maps by lump name.

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 on when to use this tool vs alternatives (e.g., map_info for querying, load_game for saved games). No prerequisites or exclusions mentioned.

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