zandronum-mcp

Overview Schema Source Related Servers Discussions Admin

Press a menu key

menu_key

Navigate menus by sending key events to the active menu. Supports arrow keys, enter, back, and backspace for selection and navigation.

Instructions

Send a single menu navigation key (GUI key event) to the active menu.

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": {
      "key": "<key>"
    },
    "name": "menu_key"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It does not disclose what happens if no menu is active, whether the action is reversible, or any error conditions. The statement implies a mutation but gives no safety or side effect details.

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, clear sentence (12 words) with no wasted words. It is front-loaded with the verb and immediately conveys the core action.

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

Completeness2/5

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

For a tool with no output schema and no annotations, the description lacks important context. It does not explain the need for an active menu, the effect of the 'instance' parameter, or the return behavior. Sibling tools suggest more context is needed for appropriate selection.

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?

Schema coverage is 0%, yet the description adds no value beyond what the schema provides. The 'key' parameter's enum values are in the schema, and 'instance' is not mentioned at all. The description fails to explain the meaning or usage of either parameter.

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

Purpose4/5

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

The description clearly states the tool sends a single menu navigation key (GUI key event) to the active menu. It uses a specific verb and resource, but does not explicitly differentiate from sibling tools like menu_nav which might handle multi-key sequences.

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 versus alternatives such as menu_nav or menu_text. The description does not mention prerequisites (e.g., an active menu) or conditions under which the tool should be chosen.

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