zandronum-mcp

by rc4l

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Player state

player_state

Retrieve a player's current position, angle, floor height, sector, and light level by running the currentpos command.

Instructions

Run currentpos and return the player's position, angle, floor height, sector, and light level.

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

Input Schema

Name	Required	Description	Default
`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 provided. Description mentions running a command but does not clarify if it is read-only, requires specific permissions, or has side effects. 'Run' may imply execution, but likely safe.

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, no extraneous information. Efficiently states the core functionality.

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?

Lists returned fields, which is useful. However, missing parameter explanation and usage context. No output schema to compensate for return value details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has one parameter 'instance' with no description. Description does not mention this parameter at all, leaving its meaning unexplained despite 0% schema coverage.

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?

Description clearly states it returns player position, angle, floor height, sector, and light level by running a specific command. Distinguishes from sibling 'actor_state' which targets actors, but could be more abstract.

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 like 'actor_state' or 'map_info'. No context about prerequisites or constraints.

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