Create a copy of an existing automation node by specifying its node ID, so you can duplicate and reuse blocks in nana800 workflows.
Create a copy of an existing node
| Name | Required | Description | Default |
|---|---|---|---|
| node_id | Yes | The node ID to copy |
Changes observed during successful MCP inspections.
v1.2.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It doesn't disclose whether the copy is deep or shallow, how it's named, whether it's auto-placed in the scheme, or whether the operation is reversible — all critical for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence, front-loaded with the action and resource, with zero filler. It is appropriately sized for what it says, though it says very little.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a mutation tool with no annotations and no output schema, the description leaves key questions unanswered: what the returned copy contains, its naming, and its placement. One-param schema simplicity helps, but the behavioral gap remains significant.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only one parameter with 100% schema description coverage ("The node ID to copy"), so the schema fully documents it. The description adds nothing beyond that, but the high coverage justifies the baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource: "Create a copy of an existing node." This clearly distinguishes it from creation siblings like node_create_action/node_create_trigger, though it doesn't say how the copy differs from node_create.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to copy versus creating a fresh node, no prerequisites, no note on where the copy lands (same scheme? parent?). The agent must infer all usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.