Skip to main content
Glama

get_voicebank

Retrieves a single VOCALOID voicebank by name or comp ID, so you can identify and use the correct voice in projects.

Instructions

One voicebank by name or comp ID. / 名前または comp ID で音源を1つ取得します

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "voice": "<voice>"
    },
    "name": "get_voicebank"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/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. It implies a read-only lookup via '取得' but does not state what happens if the voicebank is not found, whether the name match is exact or fuzzy, or what the response contains.

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 bilingual statement with the core fact front-loaded and nothing wasted. The English/Japanese duplication adds length but serves the same content, so it does not obscure meaning.

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-parameter lookup with no output schema and no annotations, the description covers the identifier semantics but leaves return shape and not-found behavior undefined. That is the minimum viable level for a simple retrieval tool, not a complete one.

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 parameter is only titled 'Voice', so the description must compensate, and it partly does by declaring that the value may be a name or a comp ID. It does not explain the comp ID format, whether both forms are unambiguous, or how name collisions are resolved.

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 states a specific verb and resource: retrieve exactly one voicebank ('One voicebank by name or comp ID', '音源を1つ取得します'), including the accepted identifier types. The singular 'one' implicitly contrasts with the sibling list_voicebanks, but that sibling is never named, so differentiation is inferential rather than explicit.

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: nothing says when to look up a single voicebank instead of enumerating them with list_voicebanks, nor what to do when the identifier is unknown. The agent must infer the lookup-vs-list split from the word 'one' alone.

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