Skip to main content
Glama
tamo2918

Minecraft Server MCP

by tamo2918
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

summon_entity

Summon Minecraft entities like zombies, villagers, or armor stands at specific coordinates using X, Y, Z positions and optional NBT data.

Instructions

Summon an entity at a position. Examples: 'zombie', 'skeleton', 'villager', 'item_frame', 'armor_stand'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entityYesEntity ID (e.g., 'zombie', 'villager')
xYesX coordinate
yYesY coordinate
zYesZ coordinate
nbtNoOptional NBT data as JSON string

Implementation Reference

  • src/tools/command-tools.ts:233-245 (handler)
    The handler function that constructs and executes the Minecraft RCON 'summon' command.
    async ({ entity, x, y, z: zCoord, nbt }) => {
  const cmd = nbt
    ? `summon ${entity} ${x} ${y} ${zCoord} ${nbt}`
    : `summon ${entity} ${x} ${y} ${zCoord}`;
  try {
    const response = await manager.rcon.send(cmd);
    return { content: [{ type: "text", text: response }] };
  } catch (error) {
    return {
      content: [
        {
          type: "text",
          text: `Failed: ${error instanceof Error ? error.message : String(error)}`,
  • src/tools/command-tools.ts:223-232 (schema)
    Zod schema defining the input parameters for the summon_entity tool.
    {
  entity: z.string().describe("Entity ID (e.g., 'zombie', 'villager')"),
  x: z.number().describe("X coordinate"),
  y: z.number().describe("Y coordinate"),
  z: z.number().describe("Z coordinate"),
  nbt: z
    .string()
    .optional()
    .describe("Optional NBT data as JSON string"),
},
  • src/tools/command-tools.ts:220-222 (registration)
    Registration of the 'summon_entity' tool in the MCP server.
    server.tool(
  "summon_entity",
  "Summon an entity at a position. Examples: 'zombie', 'skeleton', 'villager', 'item_frame', 'armor_stand'.",

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to mention side effects (e.g., spawning hostile mobs), return values (entity UUID or confirmation), error conditions (invalid coordinates), or whether this operation is reversible. The description only explains the primary intent.

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 consists of two efficient sentences: the first front-loads the core action, and the second provides concrete examples. There is no redundant or wasted text; every word earns its place.

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?

Given the 100% schema coverage, the description appropriately omits redundant parameter documentation. However, with no output schema and no annotations, it should disclose return values or side effects, which it does not. It meets minimum viability for invocation but leaves operational context gaps.

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?

With 100% schema description coverage, the baseline is 3. The description adds example entity IDs ('skeleton', 'item_frame', 'armor_stand') that supplement but largely overlap with the schema's examples ('zombie', 'villager'). It does not add semantic depth to parameters like the NBT data format or coordinate system context.

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 ('Summon') and resource ('entity') with scope ('at a position'), making the core purpose clear. However, it does not explicitly differentiate from siblings like 'give_item' (which gives items to players) or 'set_block' (which places blocks), though the verb choice provides implicit distinction.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., 'give_item' for items vs 'summon_entity' for mobs), nor are prerequisites or error conditions mentioned. The description only states the action without contextual selection criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tamo2918/Minecraft-Server-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server