Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

delete_node

Deletes a node from the currently open Godot scene using its node path, enabling scene tree cleanup and modification through AI-driven editor commands.

Instructions

Delete a node from the currently open scene.

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": {
      "node_path": "<node_path>"
    },
    "name": "delete_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_pathYesPath of the node to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a destructive operation, yet it discloses nothing about irreversibility, whether child nodes are cascaded, whether undo is possible, or what happens if node_path does not resolve. It adds no behavioral content beyond the word 'delete'.

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 front-loaded sentence with no filler; every word earns its place. Its weakness is under-specification rather than verbosity, and the scene-scoping qualifier is placed sensibly.

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 single-parameter tool with no annotations and no output schema, the definition is too thin: an agent cannot tell whether deletion is permanent, whether children go with it, or how failures are signalled. A sentence or two on those traits would make the definition complete.

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 description coverage is 100% and the single node_path parameter is documented in the schema itself, so baseline 3 applies. The description adds no syntax, format, or path-resolution detail beyond what the schema states.

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?

States a specific verb (delete) and resource (node) and scopes it to the currently open scene, which is enough to distinguish it from unrelated siblings. It does not, however, distinguish itself from batch_delete_nodes or explain the singular-vs-batch relationship.

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?

The only usage context is that the node lives in the currently open scene. There is no when-to-use guidance, no mention of when to prefer batch_delete_nodes, and no stated prerequisites such as selecting or focusing the node first.

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