Skip to main content
Glama

import_midi

Import a MIDI file into the open VOCALOID6 project as new AI or classic tracks, converting MIDI lyric events into lyrics for immediate vocal editing.

Instructions

Import a MIDI file into the open project as new tracks (track_type "ai" or "classic"; MIDI lyric events become lyrics). / MIDI ファイルを新しいトラックとして読み込みます(track_type は "ai" か "classic")

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": {
      "midi_path": "<midi_path>"
    },
    "name": "import_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
midi_pathYes
track_typeNoai
import_tempoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose real behavior: tracks are created new (additive), lyric events are mapped to lyrics, and the track type is selectable. It omits failure modes (missing/invalid file), whether import_tempo defaults matter, what happens to conflicting tempo with the existing project, and what is returned.

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

Conciseness4/5

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

Front-loaded with the action and the key side effect (lyrics from MIDI lyric events) in a single compact sentence. The Japanese sentence is a straight translation that occupies roughly half the text without adding new information, a minor redundancy.

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 three-parameter mutation tool with no annotations and no output schema, the definition covers the core effect but leaves one parameter unexplained and says nothing about return value or error conditions. Adequate to attempt a call, not sufficient to call confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for all three parameters. It only clarifies track_type (valid values "ai" or "classic") and implies midi_path, while import_tempo is never mentioned at all despite its default of true potentially altering project tempo.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Import a MIDI file into the open project as new tracks") and adds scope detail: results land as new tracks, track_type is "ai" or "classic", and MIDI lyric events become lyrics. It does not explicitly distinguish itself from conversion-oriented siblings like midi_to_note or export_midi, so sibling routing is only implied.

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?

Usage is implied rather than stated: "into the open project" hints that a project must already be open, and "as new tracks" hints the operation is additive. There is no explicit when-to-use, when-not-to-use, or named alternative among the many sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.