Skip to main content
Glama

new_project

Create an empty .vpr VOCALOID project file with optional BPM, time signature, and title; choose whether to open it in VOCALOID6 and add tracks afterward.

Instructions

Create an empty .vpr project (no tracks yet; add them with add_track). open_in_vocaloid=true opens it in VOCALOID6 (force=true discards unsaved changes there). / 空の .vpr を作成します(トラックは add_track で追加)。 open_in_vocaloid=true で VOCALOID6 で開きます(force=true で VOCALOID6 の未保存の変更を破棄)。

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

Input Schema

NameRequiredDescriptionDefault
bpmNo
pathYes
denomNo
forceNo
numerNo
titleNo
overwriteNo
open_in_vocaloidNo

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. It does well on the risky part: it discloses that force=true discards unsaved changes in VOCALOID6, which is a real destructive side effect. It says nothing about what overwrite does to an existing file at path, or about bpm/numer/denom/title defaults, so the behavioral picture is only partial.

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

Conciseness3/5

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

Each language version is tight and front-loads the key scoping fact, but the full text is duplicated verbatim in Japanese, doubling the length without adding information for a reader who understands one language. The signal-to-noise ratio per sentence is good; the redundancy is structural.

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?

For an 8-parameter creation tool with no annotations and no output schema, the description covers only the open/force behavior. It omits the semantics of overwrite and the time-signature/tempo parameters, and never says what is returned on success, so an agent cannot confidently call it with more than the required path.

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% across 8 parameters, so the description must compensate, and it only explains open_in_vocaloid and force plus the implied path. It never mentions overwrite, bpm, numer, denom, or title, leaving five parameters with no meaning anywhere in the definition.

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

Purpose5/5

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

States a specific verb and resource ('Create an empty .vpr project') and immediately scopes it ('no tracks yet'), then routes to the sibling that adds tracks (add_track). An agent can distinguish this from add_track or open_project without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear usage flow: create the empty project first, then populate it with add_track, and use open_in_vocaloid=true to hand off to VOCALOID6. It does not address when to prefer open_project or reload_project over creating a new one, but the create-then-populate sequencing is explicit.

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