minecraft-mcp

Overview Schema Source Related Servers Discussions Admin

Summon an entity

summon_entity

Spawn a Minecraft entity at chosen coordinates, or two blocks ahead of the player by default. Specify the entity type and optional position for precise placement.

Instructions

Spawn an entity (e.g. zombie, cow, armor_stand) at the given coordinates, or 2 blocks in front of the player 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>"
    },
    "name": "summon_entity"
  }
}

Input Schema

Name	Required	Description
`x`	No
`y`	No
`z`	No
`type`	Yes	Entity type key (e.g. "zombie", "cow")
`player`	No	Online player name (defaults to the first online player)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the default positioning behavior, which is a useful behavioral trait, but does not mention side effects such as world mutation, persistence, or potential failure (e.g., invalid entity type). It gives some context but lacks comprehensive transparency.

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?

The description is a single sentence that is front-loaded with the action, includes examples, and states the default behavior. Every word earns its place, with no redundancy or filler.

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?

For a tool with 5 parameters and no output schema, the description covers purpose and basic usage but omits details like whether coordinates are absolute or relative, how to specify the player, and what the return value is. This leaves some gaps for an agent trying to invoke the tool correctly.

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 only 40% (type and player have descriptions). The description adds meaning by implying x, y, z are optional (via 'or 2 blocks in front of the player by default') and provides example entity types. It does not elaborate on the player parameter beyond the schema, but the compensation for the low-coverage coordinates is helpful.

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?

The description clearly states the action ('spawn') and the resource ('entity'), with concrete examples (zombie, cow, armor_stand). It differentiates from sibling tools like interact_entity or attack by indicating a creation action, making its purpose unmistakable.

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 description provides usage context by noting that coordinates are optional and default to 2 blocks in front of the player, which guides when to omit them. It does not explicitly name alternatives, but no sibling tool performs spawning, so the usage scope is clear.

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