zandronum-mcp

by rc4l

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Navigate a menu

menu_nav

Navigate Zandronum menus by sending a sequence of key presses like up, down, and enter with a short delay between each.

Instructions

Send a sequence of menu keys (e.g. ["down","down","enter"]) with a small delay between each.

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": {
      "steps": "<steps>"
    },
    "name": "menu_nav"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Discloses a small delay between keys, but does not mention prerequisites (e.g., menu must be open) or constraints on sequence length.

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, front-loaded with action, 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?

Minimal but sufficient for a simple tool; however, lacks output schema and context on delay timing or error behavior.

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?

Describes only the 'steps' parameter with examples; the 'instance' parameter (integer, default 1) is not mentioned, and schema has no descriptions.

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 it navigates a menu by sending a sequence of keys, distinguishing from siblings like menu_key (single key) and menu_text (text input).

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, such as menu_key for single key presses or verify_menu to check menu state.

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