Skip to main content
Glama
Sign In
zandronum-mcp

zandronum-mcp

by rc4l
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Open, navigate, and screenshot a menu

verify_menu

Opens a game menu with a console command, applies navigation inputs, and returns a screenshot to verify the menu state.

Instructions

Open a menu (via a console command like menu_options), apply navigation steps, then return a screenshot to verify it.

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

Input Schema

NameRequiredDescriptionDefault
openNo
stepsNo
instanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions the sequence of actions but does not describe side effects, error behavior, or whether the screenshot is returned immediately or stored. The mechanism 'like menu_options' is vague.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that conveys the core workflow efficiently. It is front-loaded with the main action. Some additional structure (bullet points) could improve readability, but it remains concise.

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?

Given no annotations, no output schema, and complex context (multiple sibling tools), the description is incomplete. It does not specify the return format, error handling, prerequisites (e.g., game state), or how to interpret the screenshot. The tool's composition nature is not fully explained.

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%, so the description should compensate. It explains 'steps' as navigation steps with enum values, but 'open' and 'instance' are not described beyond their names. The meaning of 'open' (console command) is hinted but not specified.

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 the tool's purpose: open a menu via console command, apply navigation steps, and return a screenshot. This verb-resource combination distinguishes it from sibling tools like menu_nav or screenshot alone.

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 is provided on when to use this tool versus alternatives (e.g., menu_nav + screenshot separately). There is no mention of prerequisites or scenarios where it is appropriate or inappropriate.

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