Skip to main content
Glama
Sign In
Inochi Creator MCP

Inochi Creator MCP

by ozekimasaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

creator_set_edit_mode

Switch Inochi Creator's edit mode to model, vertex, anim, or test for targeted editing tasks.

Instructions

Switch Inochi Creator edit mode. Use model, vertex, anim, or test.

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": {
      "mode": "<mode>"
    },
    "name": "creator_set_edit_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYesTarget edit mode

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/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 states the core behavior of switching modes and lists allowed values, but it does not mention potential side effects, prerequisites like a loaded project, or whether undo state is affected. This is a notable gap for a tool with no safety profile.

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 that names the action, target, and valid values with no filler or redundancy. It is appropriately sized for the tool's simplicity.

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 tool with one enum parameter and no output schema, the description is mechanically sufficient: it tells the agent what the tool does and what values are allowed. However, it lacks usage context and behavioral caveats, making it less than fully complete for confident autonomous invocation.

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% with a self-describing enum for 'mode'. The description's 'Use model, vertex, anim, or test' simply restates the schema values without adding meaning about what each mode does or when to choose one. It meets the baseline but adds no extra semantic value.

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 the specific verb 'Switch' and the resource 'Inochi Creator edit mode', and it explicitly enumerates the four valid mode values. This clearly distinguishes it from sibling tools that set parameters or control animation.

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 tool is for changing the edit mode, but it does not explicitly state when to use it versus alternatives or provide exclusions. The instruction 'Use model, vertex, anim, or test' refers to parameter values, not tool-selection guidance.

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