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

bedrock-map-builder-mcp

by xRookieFight

set_world_rules

Configure world spawn point, gamerules, time, weather, and difficulty in one call to control Minecraft Bedrock gameplay conditions.

Instructions

Set the world spawn point and any gamerules in one go (e.g. {pvp: true, keepInventory: true, doMobSpawning: false, showCoordinates: true}).

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

Input Schema

NameRequiredDescriptionDefault
timeNo
spawnNo
weatherNo
gamerulesNo
difficultyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With empty annotations the description carries the full behavioral burden, and it only says the operation is a 'set'. It never states whether omitted fields are left untouched (critical, since all five parameters are optional), whether changes are immediate or reversible, or what permissions are required.

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?

One front-loaded sentence with no filler, and the inline example earns its place by illustrating the gamerules map format. It is efficient, though efficiency here comes at the cost of coverage rather than through disciplined editing.

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

Completeness2/5

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

For a five-parameter mutation tool with nested objects, zero schema descriptions, and no annotations or output schema, the description addresses only two of the five settings and leaves the most complex parameter (spawn) undocumented. It is not sufficient for an agent to call this correctly without reading the raw schema closely.

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% across five parameters, including a nested spawn object and two enum fields. The description's gamerule example is genuinely helpful for that one parameter (showing key names and boolean values), but time, spawn coordinates, weather, and difficulty receive no explanation at all.

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 uses a specific verb ('Set') with named resources ('world spawn point', 'gamerules'), so the core action is unambiguous. However, it omits three of the five things the schema actually controls (time, weather, difficulty), so an agent reading only the description would underestimate the tool's scope.

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?

The phrase 'in one go' implies this is a batched multi-setting operation, which is weak but real usage guidance. There is no statement of when to prefer this over separate world tools (e.g. world_create) or any prerequisites such as the world already existing.

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