Skip to main content
Glama
Sign In
Inochi Creator MCP

Inochi Creator MCP

by ozekimasaki
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

creator_import_folder

Import PNG, TGA, or JPEG images from a folder as a new project, replacing the current one.

Instructions

Import PNG/TGA/JPEG images from a folder as a new project. THIS REPLACES THE CURRENT PROJECT.

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": {
      "path": "<path>"
    },
    "name": "creator_import_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute folder path

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

The description prominently warns 'THIS REPLACES THE CURRENT PROJECT.' with all-caps emphasis, disclosing the destructive/replacing behavior that is critical for an agent to know. With no annotations provided, this covers the most important behavioral trait. It could add details about unsaved changes or undo history, but the core danger is clearly stated.

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 two sentences, front-loads the primary purpose, and uses all-caps only for the critical warning. Every word contributes meaning, with no redundancy or filler.

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

Completeness5/5

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

For a simple one-parameter tool with no output schema, the description is complete: it states the input format, the import source, the project-replacing side effect, and the target. No additional return-value or error-handling details are necessary.

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 fully describes the single parameter 'path' as 'Absolute folder path' (100% coverage). The description reinforces that it is a folder of images, but adds no additional semantic detail beyond the schema. Baseline 3 is appropriate as the schema carries the burden.

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 a specific action: 'Import PNG/TGA/JPEG images from a folder as a new project.' It names the resource (folder of images), the target (new project), and the supported formats. This distinguishes it from sibling tools like creator_import_psd or creator_import_images by specifying folder-based batch import of raster formats.

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 for importing image folders when creating a new project, but it gives no explicit guidance on when to choose this over alternatives like creator_import_images or creator_import_psd. No exclusions or conditions are provided.

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