Skip to main content
Glama
phaserjs

Phaser Editor MCP Server

Official
by phaserjs

scene-delete-plain-objects

Delete plain objects such as Tilemap, Key, or Collider from a scene by providing scene ID and object IDs.

Instructions

Delete the given plain objects from the scene. Plain objects are Tilemap, Key, Collider...

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesThe `id` of the scene. The `id` is not the name of the scene, else a unique identifier is set in the scene data. You need to read the scene data to get the `id`.
objectIdsYesThe `id`s of the plain objects to delete.
Behavior2/5

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

No behavioral details beyond 'Delete'. No annotations are provided, so the description carries the full burden but omits safety, reversibility, or side effects such as impact on dependent objects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Short but incomplete sentence ending with '...' suggests truncation. Not as concise as it could be if complete.

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?

Lacks sufficient context for a deletion tool with no output schema. Does not explain how to obtain object IDs, what happens after deletion, or how it fits with sibling tools.

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 covers both parameters with descriptions (100% coverage), so the description adds no extra value. 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 clearly states it deletes plain objects and defines them as Tilemap, Key, Collider, distinguishing it from other delete tools like scene-delete-game-objects. However, the description is truncated, which slightly reduces clarity.

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 on when to use this tool versus alternatives such as scene-delete-game-objects or scene-delete-game-object-filters. The description does not mention exclusions or prerequisites.

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/phaserjs/editor-mcp-server'

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