Skip to main content
Glama

split_lyrics

Previews how input text splits into one lyric per note so you can check lyric-to-note alignment before applying it in VOCALOID6.

Instructions

Preview how text splits into one lyric per note. / テキストが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": {
      "text": "<text>"
    },
    "name": "split_lyrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
languageNoauto

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden; 'Preview' is the one real disclosure, signaling the tool does not mutate the project. It says nothing about what the preview returns (a mapping list? counts?), whether anything is written, or how the splitting rules behave.

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 operation and its outcome. The bilingual duplication is intentional localization rather than padding, though it does double the surface length without adding new information.

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

Completeness2/5

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

For a tool with no annotations and no output schema, the description should explain what the preview yields and how the language parameter affects the split. Neither is covered, leaving the agent unable to predict the response or the effect of the second parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so both parameters are undocumented in structured data. The description only obliquely references 'text' and says nothing at all about the 'language' parameter or its 'auto' default, which likely governs how text is segmented into syllables/moras.

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 verb ('Preview') and a specific operation ('how text splits into one lyric per note'), which tells an agent exactly what computation happens. It does not, however, contrast itself with the sibling assign_lyrics, which an agent could easily confuse with a preview-only tool.

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 word 'Preview' implies this is a non-committal check performed before actually applying lyrics, which is useful implied usage guidance. There is no explicit when-to-use/when-not statement and no named alternative such as assign_lyrics for the commit step.

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