MCP server for controlling a Minecraft server via RCON protocol
Server has 9 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-60 chars, mostly under 20 chars), which violates the 20-char minimum for scoring above 0-20. Parameter descriptions are present but minimal. No output schemas documented. No error handling guidance. No input validation or constraint documentation. Tool names are verb-based (good), but descriptions lack context on WHEN to use tools, prerequisites, or what they return. No pagination for list results. No idempotency guarantees. Security concern: run_command accepts arbitrary strings with no sanitization, enabling command injection.
Broadcast a message to all players.
Get the nearest entity around a player within a given radius.
Get a list of online players.
Get the health of a player.
Get the inventory of a player.
Get the position of a player.
Give an item to a player.
run_command accepts arbitrary strings with no sanitization. Enables command injection attacks. LLM could be tricked into passing malicious Minecraft commands or RCON protocol exploits.
All tool descriptions are under 20 characters (e.g., 'Run a command on the Minecraft server.' = 40 chars but lacks WHEN to use, prerequisites, or return value details). Descriptions must be 10-1024 chars with context on selection criteria.
No output schemas documented. LLM cannot predict return structure (e.g., does get_online_players return a list, a count, or raw RCON text?). Agents cannot plan downstream calls or extract data reliably.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | <=2025-11-25 | v2 |
Run a command on the Minecraft server.
Set the time in the Minecraft world. day, night, noon
set_time description mentions 'day, night, noon' but does not declare these as an enum constraint. LLM may hallucinate invalid values like 'sunset' or '3pm'. Enums are self-documenting and prevent invalid input.
No error handling guidance. If a player is not found or a command fails, the tool returns raw RCON error text. LLM has no recovery path (e.g., 'Try search_players() first' or 'Invalid player name'). Errors must guide next steps.