Skip to main content
Glama

vocaloid_status

Check whether VOCALOID6 is running, identify the open project, and get recommended next actions before issuing further commands.

Instructions

Is VOCALOID6 running, which project is open, and what to do next. Call this first. / 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": "vocaloid_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full load. It does disclose the returned information (running state, open project, next step), implying a read-only probe, but it never says whether it has side effects, whether it errors or returns a flag when VOCALOID6 is not running, or how expensive the check is. Those omissions matter for a tool the agent is told to call before anything else.

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 content is two short sentences with the returned facts front-loaded before the 'call this first' directive. The bilingual restatement is deliberate for cross-language matching rather than padding, though it does double the token count for the same information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description substitutes by enumerating the three things the agent will learn, which is enough to decide the next step in a launch/open/status workflow. The one gap is the not-running case, where the agent cannot tell whether to expect an error or a boolean flag.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly adds no fake parameter talk.

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 the concrete facts the tool returns: whether VOCALOID6 is running, which project is open, and a recommended next action. That is more specific than a restated name, and it contrasts implicitly with project-data siblings such as get_project. It stops short of explicitly distinguishing itself from those siblings, which keeps it at 4.

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?

'Call this first' is an explicit sequencing rule that tells the agent when to reach for this tool ahead of launch_vocaloid, open_project, or get_project. There is no statement of when-not to use it or what to do if the status indicates the app is not running, but the entry-point guidance is unambiguous.

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