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

bedrock-map-builder-mcp

by xRookieFight

spawn_entities

Summon Minecraft Bedrock entities at chosen positions with optional name tags and tags so commands and functions can target them later.

Instructions

Summon entities (npc, armor_stand, villager_v2, zombie, ...) with optional name tags and tags. Tags make it easy to target them later from commands and functions.

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": {
      "entities": "<entities>"
    },
    "name": "spawn_entities"
  }
}

Input Schema

NameRequiredDescriptionDefault
entitiesYes
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and discloses very little beyond the mutation itself. It omits the 200-entity cap in the schema, what happens on an invalid entity type or out-of-range position, whether the world/server must be running, and whether spawning is reversible.

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?

Two compact sentences, front-loaded with the action and resource, then the targeting rationale. No filler, though the tag sentence could carry more practical weight given the documentation gaps elsewhere.

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 nested, mutation-style tool with no annotations, no output schema, and 0% schema coverage, the description is thin. It never explains return values (e.g., whether spawned entity IDs come back), the 200-item limit, or failure behavior, leaving the agent under-informed before invoking it.

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%, so the description must explain parameters, yet it only clarifies `name` and `tags` semantics. It says nothing about `pos` (coordinate format/units), `type` (accepted identifiers), or the `dimension` enum and its 'overworld' default.

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?

Uses a specific verb+resource ('Summon entities') and enumerates example entity types (npc, armor_stand, villager_v2, zombie), so the agent knows this creates game entities. It does not explicitly contrast with siblings such as run_commands (which could also summon via /summon), keeping it short of a 5.

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

Usage Guidelines2/5

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

The only usage-adjacent statement is that tags 'make it easy to target them later from commands and functions,' which hints at a follow-up workflow but never states when to use this tool versus run_commands or place_blocks. No exclusions, prerequisites, or alternatives are given.

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