Skip to main content
Glama
Sign In
Godot MCP Server Ultimate Edition

Godot MCP Server Ultimate Edition

by Dex865378
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

duplicate_node

Creates a copy of a node and its children in a scene, with an optional new name.

Instructions

Duplicate a node (and its children) within a 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": {
      "projectPath": "<projectPath>",
      "scenePath": "<scenePath>",
      "nodePath": "<nodePath>"
    },
    "name": "duplicate_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathYes
scenePathYes
nodePathYes
newNameNoOptional new name for the duplicate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must fully disclose behavior. It mentions duplication but does not describe what is copied (e.g., properties, signals, scripts), whether the duplicate is a sibling, or any side effects. This leaves significant uncertainty.

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?

The description is a single sentence, concise and front-loaded. However, for a tool with 4 parameters and no annotations, it could be slightly more informative without losing conciseness.

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?

The description lacks essential context: the location of the duplicate, whether all properties are copied, required permissions, and return value. Given no output schema, the description should hint at the result. The complexity (4 params, no annotations) demands a richer description.

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

Parameters2/5

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

Schema description coverage is 25% (only 'newName' has a description). The tool description adds no additional parameter information beyond the schema. For a tool with 4 parameters and low schema coverage, the description should compensate but fails to do so.

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 the action ('Duplicate') and the resource ('a node (and its children) within a scene'). It distinguishes from sibling tools like remove_node and rename_node.

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 explicit guidance on when to use this tool versus alternatives. The description only states what it does, implying usage but providing no context about prerequisites or conditions.

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