Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

server_console

Send raw commands to the Bedrock Dedicated Server console and return its immediate output for save, list, reload, and other console-only operations.

Instructions

Send a raw line to the BDS console and return what it printed for a moment after (for save, list, reload and other console only commands). In-game commands are better sent with run_commands.

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": {
      "line": "<line>"
    },
    "name": "server_console"
  }
}

Input Schema

NameRequiredDescriptionDefault
lineYes
wait_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden. It does disclose the read-back behavior ('return what it printed for a moment after'), which is genuinely useful, but it never says the tool executes arbitrary server-level console commands, what happens on an invalid line, or how the capture window relates to wait_ms.

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?

A single tight sentence with the core action front-loaded and the routing hint at the end. The parenthetical bundling of use cases is slightly dense but nothing is wasted.

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?

For a two-parameter tool with no annotations and no output schema, the description covers purpose, return behavior, and the sibling alternative adequately. It falls short on the meaning of wait_ms and on the risk profile of executing arbitrary console lines, both of which an agent needs before calling.

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 description coverage is 0% for two parameters, so the description must compensate and does not. 'line' is loosely inferable from 'raw line', but wait_ms is never mentioned and the 50-10000 ms range and its effect on the returned output are left entirely to the schema constraints.

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?

States a specific verb and resource ('send a raw line to the BDS console') plus what it returns ('return what it printed for a moment after'), and explicitly contrasts itself with run_commands. An agent can distinguish it from its siblings without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete positive cases ('save, list, reload and other console only commands') and names the alternative tool for in-game commands. The exclusion is phrased softly ('are better sent with') rather than as a hard rule, so it stops just short of full when/when-not guidance.

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