Skip to main content
Glama
Sign In
Inochi Creator MCP

Inochi Creator MCP

by ozekimasaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

creator_duplicate_node

Duplicate a node and its children, excluding cameras, to quickly replicate parts of your Inochi Creator project.

Instructions

Duplicate a node and its children (cameras cannot be duplicated).

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": {
      "uuid": "<uuid>"
    },
    "name": "creator_duplicate_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesNode UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses a key limitation (cameras cannot be duplicated) and the recursive scope (children), but does not mention return value, parameter copying behavior, or undo interactions with sibling tools like creator_undo. Some context is added, but significant gaps remain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence with no wasted words. The action, scope, and a critical exception are all conveyed efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple 1-param mutation tool with no annotations, the description gives the core action and one limitation but omits details about return values, effects on the duplicated node's properties, or relation to undo/redo. It is adequate but leaves gaps.

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?

The schema already provides 100% coverage with 'Node UUID'. The description's 'Duplicate a node' adds minimal new meaning beyond confirming that the uuid identifies the node to duplicate, so the baseline of 3 is appropriate.

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 uses a specific verb and resource: 'Duplicate a node and its children', clearly distinguishing it from sibling tools like creator_create_node or creator_delete_node. The camera exclusion adds further specificity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the use case (copy an existing node with its children) but provides no explicit guidance on when to use this tool over alternatives such as creator_create_node or creator_reparent_node. It only notes that cameras cannot be duplicated, not a usage condition.

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