Skip to main content
Glama

Summon entity

summon_entity

Spawns a Minecraft entity at exact X/Y/Z coordinates in the main world and returns its UUID for use by other entity operations.

Instructions

Spawn an entity in the main world and return its UUID (used by every other entity tool).

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": {
      "entity_type": "<entity_type>",
      "x": "<x>",
      "y": "<y>",
      "z": "<z>"
    },
    "name": "summon_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesExact X; block centres are at .5 (e.g. 100.5).
yYesExact Y of the feet.
zYesExact Z; block centres are at .5 (e.g. -20.5).
entity_typeYesEntity type such as 'zombie', 'villager' or 'minecraft:armor_stand'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and the description usefully adds that spawning is scoped to the main world, which is behavioral context the annotations do not carry. It does not mention permission/cheat requirements, what happens if entity_type is unsupported, or whether the spawn fails on blocked space — and with an output schema present, the UUID return claim is largely redundant.

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?

One short sentence, front-loaded with the action and followed by the single most decision-relevant fact (the UUID). No filler, no restatement of the title.

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 4-required-parameter creation tool with full schema coverage, an output schema, and safety annotations, the description covers purpose, world scope, and the return contract concisely. Only error/permission behavior is left unaddressed, which is a minor residual gap given the structured data already supplied.

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 coordinates (including the .5 block-centre convention and Y-as-feet) and entity_type format are already thoroughly documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Spawn an entity in the main world') and adds a distinguishing detail — it returns a UUID that every other entity tool consumes — which separates it from get_entity, remove_entity and the set_* siblings without opening their schemas.

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?

The parenthetical 'used by every other entity tool' tells the agent this is the entry point whose returned UUID feeds later calls, giving clear operational context. It stops short of explicit exclusions (e.g. when to prefer cloning or moving an existing entity instead of spawning a new one).

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