Skip to main content
Glama

export_midi

Exports the open VOCALOID project as a standard MIDI file, including lyrics, so you can reuse melodies and vocal notes in other music software.

Instructions

Export the open project as a standard MIDI file (with lyrics). / 開いているプロジェクトを MIDI ファイルに書き出します

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": {
      "output": "<output>"
    },
    "name": "export_midi"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/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 usefully discloses that lyrics are included in the output, which is real behavioral information beyond the schema, but it says nothing about where the file is written, whether existing files are overwritten, or what permissions/connection state are needed.

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?

Short and front-loaded, with the key verb and format in the opening clause. The bilingual restatement adds length without new information, but it is a minor redundancy rather than clutter.

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

Completeness2/5

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

With no annotations, no output schema, and an undocumented required parameter, the description leaves too much unspecified for a file-writing operation. An agent cannot determine the semantics of the output path or the side effects of the export from this definition alone.

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% and the sole required parameter ('output') is completely undocumented in both schema and description. The description never explains that 'output' is presumably the destination path or what format it should take, so the documented meaning is missing for the one input that matters.

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?

States a specific verb and resource ('Export the open project') plus the output format ('standard MIDI file'), and the '(with lyrics)' qualifier separates it from a plain MIDI export. It does not name siblings like export_vsqx or export_wav, but the format naming is enough for an agent to distinguish intent.

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 phrase 'the open project' implies a prerequisite context (a project must be open) and the intent is clear from the verb, but there is no explicit when-to-use/when-not guidance and no routing to alternative exports. The agent must infer that export_wav/export_vsqx are the options for other formats.

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