Skip to main content
Glama

game_delete_entity

Destructive

Delete a bridge-spawned entity by ID to remove it from the game world, with optional player and server targeting.

Instructions

Delete a bridge-spawned entity by ID

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": {
      "entityId": "<entityId>"
    },
    "name": "game_delete_entity"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerNo
serverNo
entityIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral constraint — that only bridge-spawned entities are eligible — but says nothing about irreversibility, failure behavior for non-spawned IDs, or whether removal is immediate.

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?

A single short phrase with zero filler, and the distinguishing qualifier is front-loaded. It is a fragment rather than a sentence, which is fine for a tool this narrow, though a few more words on preconditions would have earned their place.

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 destructive three-parameter tool with no output schema and zero schema descriptions, the definition is too thin. An agent still cannot tell how player/server select the target, what happens on an invalid or non-bridge ID, or whether the deletion is reversible.

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 carries the full burden, and it only clarifies the meaning of entityId ('by ID'). The player and server parameters — which appear to scope the target game instance — are completely unaddressed in both schema and description.

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 gives a specific verb ('Delete') and resource ('entity') plus a qualifying scope ('bridge-spawned ... by ID'), which lets an agent distinguish it from generic deletion like resource_delete or from spawning with game_spawn. It does not explicitly name a sibling, but the qualifier does the differentiating work.

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 explicit statement of when to use this versus alternatives, nor any when-not guidance. The phrase 'bridge-spawned' implies a precondition (only entities created through the bridge/spawn path can be deleted), but this is left for the agent to infer rather than stated as a rule.

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