Skip to main content
Glama
Sign In
Phaser Editor MCP Server

Phaser Editor MCP Server

Official
by phaserjs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ide-create-new-scene

Create a new scene file for a Phaser game. This generates the file with the correct extension; afterwards, add the scene to the game instance.

Instructions

Create a new scene file. This tool only creates a new scene. If the user wants to show the scene in the game then the user has to add the scene first to the game instance.

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": {
      "name": "<name>"
    },
    "name": "ide-create-new-scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the scene file. It is not a full name, just the name. The extension will be added automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

A4.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It discloses that it only creates a scene file and does not display it, but it doesn't mention potential side effects like overwriting existing files or checking for name collisions. Adequate but not comprehensive.

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?

Two sentences, no wasted words. Front-loaded with the core purpose, followed by a crucial usage note. Very efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given only one parameter and no output schema, the description is complete. It explains what the tool does and a key usage condition. No gaps.

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?

The parameter 'name' has a helpful description that clarifies it's just the base name, not a full path, and that the extension is added automatically. Since schema coverage is 100% and the description adds meaning beyond the schema, it scores well.

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 it creates a new scene file, distinguishing it from siblings like ide-open-scene or scene-get-scene-data. It uses a specific verb and resource.

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?

It explicitly notes that creating a scene does not show it in the game, and that adding it to the game instance is a separate step. This provides clear context for when to use this tool vs. other scene-related tools.

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

Deploy Server

Other Tools