Skip to main content
Glama
Godot MCP Server

Godot MCP Server

by neondeex

duplicate_node

Creates a copy of a scene node at a specified path, optionally assigning a new name for the duplicated node.

Instructions

Duplicate a node in the 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": "duplicate_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
new_nameNoName for the duplicated node
node_pathYesPath of the node to duplicate

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?

With no annotations, the description carries the full behavioral burden and provides almost nothing: it does not say whether children/connections are copied, where the copy is placed in the tree, or what happens if the name collides. It also gives no indication of a returned reference or path to the new node.

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 zero filler, but the brevity reflects under-specification rather than disciplined pruning. There is no structure beyond the bare statement of action.

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 an unannotated mutation tool with no output schema, the description should say more about effects (deep vs shallow copy, naming behavior if new_name is omitted, what is returned). An agent cannot call this confidently without guessing at these behaviors.

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%, so both node_path and new_name are already documented in the schema. The description adds no meaning beyond that — nothing about path format, whether new_name is required, or what the default name would be if omitted.

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 (duplicate) and resource (a node in the scene), so the agent knows exactly what action is performed. It does not differentiate from near-siblings such as add_node, rename_node, or move_node, which share the same node-editing domain.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives like add_node (for creating a fresh node) or rename_node. The agent must infer the selection criterion from the name alone.

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