Skip to main content
Glama
Sign In
Godot MCP Bridge

Godot MCP Bridge

by farrasfadhils
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

delete_scene

Delete Godot scene files programmatically through AI assistants. Removes specific scenes from game engine projects via the Godot MCP Bridge.

Instructions

Delete a scene file. (Compatibility tool)

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
timeoutMsNo
autoConnectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies destruction, the description fails to clarify whether this removes the file from disk or just the project, whether it is reversible, or why connection-related parameters (timeoutMs, autoConnect) are present. The 'compatibility' label is unexplained.

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?

The description is extremely brief (two short segments), which qualifies as concise, but the '(Compatibility tool)' addition lacks sufficient context to earn its place. The structure is front-loaded but overly terse given the complexity of a destructive file operation.

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 operation with undocumented parameters and no output schema, the description is dangerously incomplete. It lacks safety warnings, return value documentation, and explanation of the connection-oriented parameters (timeoutMs/autoConnect) evident in the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both parameters, yet the description provides no compensatory information. Crucially, it fails to explain how to specify which scene file to delete (the schema allows additionalProperties, suggesting a path/name parameter exists but is undocumented), rendering the tool potentially unusable without trial and error.

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 the core action ('Delete') and resource ('scene file'), distinguishing it from sibling tools like 'delete_node' or 'remove_animation'. However, the parenthetical '(Compatibility tool)' is cryptic and unexplained, slightly diminishing 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 is provided on when to use this tool versus alternatives like 'remove_autoload' or 'save_scene', nor does it explain the significance of it being a 'compatibility' tool. No prerequisites or warnings are included.

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