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

bedrock-map-builder-mcp

by xRookieFight

plan_create

Save a multi-step build plan for large Minecraft Bedrock map projects, with steps as ordinary tool calls, so work survives restarts and can resume where it stopped.

Instructions

Save a multi step build plan (big projects: terrain, then districts, then roads, then details). Steps are ordinary tool calls. Plans survive restarts and plan_run continues where it stopped.

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": {
      "title": "<title>",
      "steps": "<steps>"
    },
    "name": "plan_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepsYes
titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two meaningful traits: plans persist across restarts, and plan_run resumes from the stopping point (implying creation alone does not execute the steps). It does not state whether creating a plan with an existing title overwrites, errors, or duplicates, nor what identifier or result comes back.

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?

Three short sentences with the core action front-loaded, then a clarifying example, then the persistence/resume behavior. The parenthetical example is long but earns its place as concrete guidance; nothing is redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with no annotations and no output schema, the description covers the essential mental model: what a plan is, that steps are tool calls, that plans persist, and that plan_run resumes them. The main remaining gaps are overwrite/duplicate semantics on the title and what plan_create returns.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate; it partially does by explaining that 'steps' are 'ordinary tool calls', which clarifies the items are calls to other tools rather than free text. It adds nothing about the 'title' parameter, the per-step 'note' or 'args' objects, or the 500-step ceiling.

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 states a specific verb and resource ('Save a multi step build plan') and gives a concrete example of its content shape (terrain, districts, roads, details). It also implicitly distinguishes itself from plan_run by noting that plan_run resumes where the plan stopped, so creation and execution are separable.

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?

It gives implied when-to-use context ('big projects') and the example sequence, which helps an agent decide a plan is worthwhile. It does not explicitly say when not to use it versus plan_edit for changes or plan_list/plan_show for inspection, leaving the agent to infer the boundaries.

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