Skip to main content
Glama

list_styles

Lists available VOCALOID6 style presets, optionally filtered by name, so you can choose the right style to apply in the part inspector.

Instructions

VOCALOID6 style presets (e.g. filter="Soft"). Apply them in VOCALOID6's part inspector. / VOCALOID6 のスタイルプリセット一覧(例 filter="Soft")。適用は 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": "list_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/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 disclose the key scope boundary that applying presets happens outside this tool. However, it says nothing about whether the call is read-only in effect, whether filtering is exact or substring matching, or what happens with no filter.

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?

Two short sentences, front-loaded with the resource and an inline example. The bilingual duplication is redundant for an English reader but plausibly intentional for a Japanese product, and no sentence is wasted.

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 one-optional-parameter list tool with an output schema (so return values need no explanation), this is close to adequate. The remaining gap is filter semantics, which neither the schema nor the description covers.

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 coverage is 0% and the single 'filter' parameter has no schema description, so the description's example filter="Soft" is the only signal that filter takes a style name. It does not clarify matching semantics or default behavior when filter is null.

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 resource (VOCALOID6 style presets) and the Japanese half makes the listing action explicit (一覧). It is distinguishable from siblings like list_notes and list_voicebanks by resource, though the English sentence has no explicit verb.

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 clause 'Apply them in VOCALOID6's part inspector' usefully tells the agent this tool only retrieves presets and that application is manual, but there is no explicit when-to-use or when-not-to-use guidance versus other tools, and no instruction on when to supply a filter.

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