Skip to main content
Glama

save_project

Saves the open VOCALOID6 project. Pass a .vpr file path to save it to that location as a new file.

Instructions

Save the project open in VOCALOID6; with a .vpr path, save it there (Save As). / VOCALOID6 のプロジェクトを保存します。.vpr のパスを渡すとその場所に保存します(名前を付けて保存)。

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

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the Save As versus overwrite-in-place distinction, but says nothing about whether an existing file is overwritten, what happens with an invalid or non-.vpr path, or what is returned on success/failure — significant gaps for a disk-writing mutation.

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?

The English sentence comes first and states the core behavior plus the mode switch in one line. The Japanese translation doubles the length without adding information, but that appears to be an intentional bilingual convention 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 single optional parameter with no annotations and no output schema, the description covers the main behavioral fork but leaves error conditions, overwrite policy, and return behavior unspecified. An agent could invoke it correctly in the happy path but would not know how to handle failures.

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 description coverage is 0%, and the schema only declares an optional nullable string named 'path'. The description adds the key semantics — the value should be a .vpr path and supplying it triggers Save As while omitting it saves in place — but does not say whether the directory must exist or whether the extension is enforced.

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?

The description names a specific verb and resource ('Save the project open in VOCALOID6') and even splits the behavior into save-in-place versus Save As. It does not explicitly contrast itself with siblings like open_project or new_project, but the operation is unambiguous from the text alone.

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?

It gives a clear conditional rule: call with a .vpr path to perform Save As, omit the path to save in place. That is enough for an agent to choose the right invocation mode, though it never states preconditions (e.g. a project must already be open) or the case where saving should be avoided.

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