Skip to main content
Glama

Spawn entities

spawn_entity

Creates one or more Minecraft entities at a chosen location so you can populate worlds or test server scenarios; supports counts, worlds, and attributes.

Instructions

Spawn one or more entities of a type, such as minecraft:cow, at a location. The server caps the count (50 by default).

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": {
      "type": "<type>",
      "location": "<location>"
    },
    "name": "spawn_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
aiNoLiving entities only
typeYesEntity key
countNoCapped at 50 by default
worldNoWorld name, such as `world`, `world_nether`, `world_the_end`, or a key like `minecraft:the_nether`world
formatNo`minimessage` reads tags like `<green>Hi` or `<bold>`; `plain` sends the text as isplain
glowingNoGlowing outline
locationYesA spot in a world; y is height (the overworld runs from -64 to 319)
customNameNoName tag
persistentNoDon't despawn

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.2.1
    • addedInput schema / properties / ai / description
      Added value: +"Living entities only"
    • addedInput schema / properties / count / description
      Added value: +"Capped at 50 by default"
    • addedInput schema / properties / customName / description
      Added value: +"Name tag"
    • addedInput schema / properties / glowing / description
      Added value: +"Glowing outline"
    • addedInput schema / properties / type / description
      Added value: +"Entity key"
  2. First observedv4.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint false, destructiveHint false, idempotentHint false), so the description does not need to restate safety. It adds the server-side count cap (50), but that is also present in the `count` schema description, and it says nothing about what happens to spawned entities on restart, whether the call returns entity identifiers, or failure modes for invalid types.

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?

Two short sentences, front-loaded with the core action, with the cap in a separate sentence. No filler or redundancy in phrasing.

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?

With nine parameters, a nested location object, and no output schema, the description covers the essentials (what it spawns, where, and the count cap). However, it omits what the call returns (entity IDs/handles), whether world/location mismatch matters, and any preconditions, leaving gaps an agent would care about for this multi-param mutation.

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 100%, so the schema already documents all nine parameters, including the `location` nested object and the `world`/`format` semantics. The description only adds the entity-key example format (`minecraft:cow`), which is marginal value over the schema. Baseline 3 is appropriate.

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 (spawn) and resource (entities of a type) and gives a concrete example key (`minecraft:cow`) plus a location target. An agent can distinguish it from siblings like `remove_entity` or `update_entity`. It stops short of naming an explicit alternative, but the operation is unambiguous.

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?

There is no when-to-use guidance, no prerequisites (e.g. entity type validity, chunk loading, permissions), and no mention of alternatives such as `run_command` with `/summon` or `update_entity` for existing entities. The only context is the count cap, which is a constraint rather than usage guidance.

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