zandronum-mcp

by rc4l

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Type into a menu text field

menu_text

Enter a string into the active in-game menu input field by sending each character as a separate keystroke.

Instructions

Type a string into the active menu text-entry field (e.g. the player name box after pressing enter on it), one character at a time.

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": {
      "text": "<text>"
    },
    "name": "menu_text"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 26, 2026

TDQS

B3.2/5.0

Behavior3/5

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

The description reveals that typing happens one character at a time, which is a behavioral detail. However, with no annotations provided, it lacks information on side effects, error conditions (e.g., no active field), or required permissions.

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 of 28 words, front-loading the key information. Every word is functional with no redundancy.

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 output schema and no annotations, the description should cover return behavior, prerequisites (e.g., field must be active), and error handling. It omits all of these, making it incomplete for safe agent use.

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 schema has 0% description coverage, and the description only says 'Type a string', adding no value beyond the parameter name 'text'. The 'instance' parameter is not explained at all, leaving its purpose unclear.

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 it types a string into the active menu text-entry field one character at a time. The verb ('type') and resource ('menu text-entry field') are specific, but it does not distinguish from sibling tools like 'menu_key' which may perform similar actions.

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 implies it should be used when needing to input text into a menu text field, but it does not provide explicit guidance on when not to use (e.g., for single key presses) or mention alternatives like 'menu_key'.

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