Skip to main content
Glama
Sign In
Inochi Creator MCP

Inochi Creator MCP

by ozekimasaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

creator_get_node

Retrieve a node by UUID to obtain its transform and type-specific fields for detailed inspection and editing.

Instructions

Get one node by UUID, including transform and type-specific fields.

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_get_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesNode UUID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/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 clearly indicates this is a read operation ('Get') and discloses the return content (transform and type-specific fields). It does not mention error behavior (e.g., if UUID is not found), but for a simple getter this is sufficient additional context.

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?

The description is a single, front-loaded sentence with no wasted words. It precisely states the operation, the target, and what is included.

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

Completeness4/5

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

For a low-complexity tool with one parameter and no output schema, this description is nearly complete: it names the input (UUID) and the output content (transform and type-specific fields). It omits potential error cases, but given the simple nature, this is adequate.

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 coverage is 100%; the schema already describes the 'uuid' parameter as 'Node UUID'. The description only repeats 'by UUID' without adding further meaning about format, constraints, or behavior, so it does not go beyond the structured field information.

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 ('Get') and resource ('one node by UUID'), and explicitly mentions the included fields ('transform and type-specific fields'). This clearly distinguishes it from siblings like creator_list_nodes (which lists nodes) and creator_select_node (which selects).

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 usage when a single node's UUID is known and full details are needed, but it does not explicitly state when to use this instead of alternatives like creator_list_nodes or creator_select_node. No exclusions or alternative tools are mentioned.

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