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

bedrock-map-builder-mcp

by xRookieFight

op_undo

Destructive

Undo a Minecraft Bedrock map edit by restoring previous blocks. Reverts the newest unundone edit by default, and refuses overlapping later edits unless forced.

Instructions

Undo an edit by putting back what was there before. Refuses when a later edit overlaps it (undo that first) unless force. Without op_id it undoes the newest edit that isn't undone yet.

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

Input Schema

NameRequiredDescriptionDefault
forceNo
op_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only say destructiveHint=true; the description adds genuinely non-inferable behavior: the refusal condition on overlapping later edits, the force escape hatch, and the default target selection. It does not state whether an undo is itself undoable or what the call returns, but the precondition and override logic are the important disclosures for a mutation tool.

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?

Three short sentences, front-loaded with the core action, then the failure mode, then the default. Every clause carries distinct information with no repetition of the tool name or schema.

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 two-parameter destructive mutation with no output schema, the description covers what the agent needs to invoke it correctly: default targeting, refusal conditions, and the force override. Minor omissions are the source of op_id values and the resulting state/return after a successful undo.

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

Parameters4/5

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

Schema coverage is 0%, so the description must carry both parameters, and it does: op_id is defined by its absence ('without op_id it undoes the newest edit that isn't undone yet') and force by its conflict-override role. The only gap is the format/source of op_id values, which is left implicit.

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 ('Undo an edit') plus the mechanism ('putting back what was there before'), which is far more informative than the bare name. It does not name or contrast with any sibling, though the sibling list contains no obvious competing undo/redo tool, so the practical ambiguity is low.

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?

It gives concrete selection guidance: call with no op_id to target the newest un-undone edit, and handle the case where a later overlapping edit blocks the undo ('undo that first') unless force. The 'unless force' clause effectively routes the agent to the force parameter. What's missing is any pointer to where op_id values come from (e.g., op_list).

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