Skip to main content
Glama

self_check

Verifies that the VOCALOID6 menus and buttons required by live tools are present, helping detect compatibility issues before running operations.

Instructions

Check that the menus and buttons the live tools use still exist in this VOCALOID6 version. / ライブ操作が使うメニューとボタンがこの 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": "self_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 present, so the description carries the full disclosure burden. It does establish that this is a verification of existing UI elements against a specific VOCALOID6 version, which implies a read-only probe against the running application, but it does not state whether it launches or touches VOCALOID, whether it is safe, what happens when elements are missing, or what the result looks like. That is meaningful context, but an incomplete safety and outcome profile.

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

Conciseness5/5

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

There is a single front-loaded sentence, duplicated in Japanese for localization. There is no padding, hedging, or redundant restatement of the tool name, and the core action leads the definition.

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?

The tool is a simple zero-parameter check, but because there is no output schema, the description should explain what a pass or fail looks like. It does not, so an agent cannot tell whether the result enumerates missing elements or returns a single boolean. Everything else needed to invoke it is present.

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 and the baseline is 4. The description neither misleads nor omits any parameter meaning, because the tool accepts no arguments.

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 uses a concrete verb and object: it checks whether the menus and buttons that the live (UI-driving) tools rely on still exist in the current VOCALOID6 version. This is clearly a compatibility or precondition probe, which is distinct from all the note, part, and project-editing siblings. It falls short of a 5 only because the phrase 'the live tools' is left undefined and the description does not say what the check yields.

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?

The usage context is implied: run this before relying on UI automation, since the live tools depend on those menus and buttons. However, the description gives no explicit trigger, no prerequisites to satisfy beforehand, and no guidance for when to skip the check. The agent must infer the condition from the phrase 'live tools'.

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