Skip to main content
Glama

launch_vocaloid

Start VOCALOID6 and optionally open a .vpr or .vsqx project file. If the editor is already running, the project opens in that existing session instead of a new one.

Instructions

Start VOCALOID6 (optionally opening a .vpr/.vsqx). If it is running, opens the project there. / VOCALOID6 を起動します(.vpr/.vsqx を指定可)。起動済みならそのプロジェクトを開きます。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "launch_vocaloid"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/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 it does disclose a meaningful state-dependent behavior: an existing instance is reused rather than a second one started. It omits what happens on failure (VOCALOID6 not installed, invalid path), whether the call blocks until launch completes, and any permissions or timing caveats.

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 short sentences per language, launch behavior front-loaded before the conditional branch. The bilingual duplication is justified by the tool's audience and costs little; nothing is padded.

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 one-optional-parameter launcher with no annotations and no output schema, the description covers the essential call semantics. It is still thin on return information (does it report the launched process, PID, or status?) and on error behavior, which an agent needs to verify success.

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% and the only schema text is 'Project Path', so the description must compensate. It does add real meaning by naming the accepted formats (.vpr/.vsqx) and marking the argument optional, but it says nothing about absolute vs relative paths, whether unsupported extensions are rejected, or what happens when omitted beyond 'launch only'.

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?

Uses a concrete verb and resource ('Start VOCALOID6') and immediately scopes the optional side effect (opening a .vpr/.vsqx). It distinguishes itself from a pure project-opening tool by making the application launch primary, though it never names the sibling open_project, so the boundary 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?

States the two operating modes: cold start and, if already running, opening the project in the existing instance. That gives usable context, but it offers no explicit when-to-use/when-not guidance relative to open_project or new_project, leaving the agent to infer which entry point to pick.

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