Skip to main content
Glama

play

Starts VOCALOID6 audio so users can audition vocal tracks and edits directly from Claude without manually operating the editor.

Instructions

Start playback in VOCALOID6. / VOCALOID6 で再生を開始します

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior2/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, and it discloses almost nothing: it does not say whether the call blocks while playback runs, what happens if playback is already active, or what is returned on success or failure. For a zero-parameter transport action this is a meaningful gap, since an agent cannot predict whether the tool is fire-and-forget or long-running.

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 definition is a single short statement front-loaded with the verb, with no filler. The only mild redundancy is the bilingual restatement, which adds length without adding information.

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 simple zero-parameter action with no output schema, the definition covers the essentials but omits environment prerequisites and the effect on subsequent tool calls during playback. An agent can invoke it, but cannot reason about state transitions or error cases.

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?

The tool takes zero parameters, so baseline is 4 and there is nothing the description could add on that front. It correctly implies no arguments are required to start playback.

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 plus resource ('Start playback in VOCALOID6'), so the agent knows this triggers transport playback rather than editing notes or exporting. It does not distinguish itself from a stop/pause-style sibling, but no such sibling is named in the catalog, so the gap is minor.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisite stated (e.g. whether a project must be open or VOCALOID6 running), and no exclusion or alternative named. The only usage signal is implied by the word 'playback'.

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