Skip to main content
Glama

export_vsqx

Writes a .vsqx file for the VOCALOID4 or VOCALOID3 editor, exporting only classic VOCALOID tracks and shifting positions by one pre-measure bar to match editor timing.

Instructions

Write a .vsqx for the VOCALOID4 (version=4) or VOCALOID3 (version=3) editor. Only classic VOCALOID tracks are written; positions shift by one pre-measure bar, as those editors count. / VOCALOID4(version=4)または VOCALOID3(version=3)用の .vsqx を書き出します。VOCALOID トラックのみ。位置はプリメジャー1小節分ずれます。

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

Input Schema

NameRequiredDescriptionDefault
pathNo
outputYes
versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior4/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 two non-obvious behaviors: non-classic VOCALOID tracks are silently excluded, and positions are shifted by one pre-measure bar. It does not cover overwriting of an existing file, failure modes, or whether the editor must be running, so it is strong but not complete.

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?

Two compact sentences, front-loaded with the action and artifact and followed by the two behavioral caveats; every clause carries information. The bilingual duplication doubles length but plausibly serves language matching rather than padding.

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 no-annotation, no-output-schema mutation tool the description is adequate on behavior but incomplete on I/O: the required output target and the purpose of the optional path parameter are unexplained, which is the biggest risk when invoking a file-writing tool.

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 0%, so the description must compensate; it does explain the version parameter's meaning (3 vs 4 maps to the target editor). However, it says nothing about the distinction between the required 'output' and the nullable 'path' parameters, which is the main ambiguity an agent faces here.

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 artifact ('Write a .vsqx') plus the target editors and version mapping, so an agent knows exactly what it produces. It does not explicitly contrast itself with sibling exporters like export_midi or export_wav, which keeps it short of a 5.

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 definition scopes usage ('Only classic VOCALOID tracks are written') and identifies the consuming editors, which implies when the tool is appropriate. It gives no explicit when-not-to-use rule or pointer to the other export_* siblings, so selection between exporters is left to the agent.

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