Skip to main content
Glama

open_project

Opens a VOCALOID6 .vpr or .vsqx project file; set force=true to discard unsaved changes in the current project.

Instructions

Open a .vpr or .vsqx in VOCALOID6. force=true discards unsaved changes in the current project. / .vpr または .vsqx を VOCALOID6 で開きます。force=true で現在の未保存の変更を破棄します。

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": "open_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
forceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.5/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 the key destructive trait: force=true discards unsaved changes in the current project. It does not say what happens when unsaved changes exist and force is false, whether the currently open project is replaced or closed, or what the call returns.

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 front-loaded sentences covering action then the risky parameter, with no filler. The line is repeated verbatim in Japanese, which doubles length but serves the tool's bilingual audience rather than adding noise.

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?

No output schema and no annotations, so the description must cover behavior on its own; it handles the force hazard but leaves the preconditions (app running, existing unsaved state with force=false) and return value unexplained. Adequate for a simple two-parameter load call, but not complete.

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

Parameters4/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: it fully explains force (unsaved-change discard, default false) and characterizes path as pointing to a .vpr or .vsqx file. Only the expected path format (absolute/relative, extension handling) is left unstated.

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 (open) and resource (a .vpr or .vsqx project in VOCALOID6), and the accepted file extensions help distinguish it from generic project tools. It does not explicitly contrast itself with siblings like new_project or reload_project, but the file-loading scope is unambiguous.

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 by the file-extension constraint, but there is no explicit when-to-use vs. new_project, reload_project, or get_project, and no stated prerequisites such as whether VOCALOID6 must already be running or whether the file must exist on disk.

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