Skip to main content
Glama

list_voicebanks

Lists installed VOCALOID3–6 voicebanks with name, comp_id, kind, era, languages, and track type, optionally filtering by kind.

Instructions

Installed VOCALOID3-6 voicebanks: name, comp_id, kind (ai/classic), era, languages, track type. / インストール済みの VOCALOID3〜6 音源(名前・comp_id・種類・世代・言語・トラック種別)

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_voicebanks"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo

Output Schema

NameRequiredDescriptionDefault
resultYes

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 burden, and it discloses almost nothing behavioral beyond the field list. It does not say whether a running VOCALOID instance is required (relevant given launch_vocaloid/close_vocaloid siblings), whether results are filtered by the current project, or how the 'installed' set is determined. It is by nature a safe read, but that is implied rather than stated.

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?

A single compact field-list sentence, front-loaded with the resource and scope, with zero filler. The parallel Japanese line doubles the length for what is the same content, which is a mild cost against conciseness.

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 low-complexity, zero-required-parameter list tool with an output schema covering return values, the essentials are present and the one parameter is glossed. What is missing is preconditions — whether VOCALOID must be open and whether the list is project-scoped — which matters in a catalog that also contains launch/close tools.

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?

Schema coverage is 0% and the single parameter 'kind' is an undescribed anyOf string/null with no enum, so the description is the only source of meaning — and it delivers, glossing kind as 'ai/classic'. That is genuine added value an agent could not get from the schema.

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 with scope: 'Installed VOCALOID3-6 voicebanks', and enumerates the returned fields, so an agent knows exactly what universe of items it gets. It stops short of differentiating itself from the sibling get_voicebank (single-voicebank lookup), which is the one thing that would push this to a 5.

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 statement at all — nothing says to call this before choosing a voicebank for add_track or to prefer it over get_voicebank when only one item is needed. The agent must infer the use case entirely from the noun phrase.

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