mcp-svstudio

Overview Schema Source Related Servers Discussions Admin

set_phonemes

Assign formal SynthV phoneme strings directly to notes, fixing lyric joining issues from MusicXML imports.

Instructions

Directly assign formal SynthV space-separated phoneme strings to notes (e.g. '.sh er', '.n ax', 'g u: t'). Solves MusicXML lyric joining issues.

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": {
      "assignments": "<assignments>"
    },
    "name": "set_phonemes"
  }
}

Input Schema

Name	Required	Description
`dry_run`	No
`groupIndex`	No
`trackIndex`	No
`assignments`	Yes	List of phoneme assignments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description must convey behavior. It states the action is a direct assignment (a write operation) and gives a specific purpose, but omits details on idempotency, validation, side effects, or return values. This is a moderate gap for a mutation tool.

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?

Two concise sentences with the primary action and examples front-loaded, followed by the use case. No wasted words, well structured.

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?

Given the complexity (4 parameters, nested objects, no output schema), the description does not provide sufficient context to understand parameter relationships, required fields, or how to specify notes. It is incomplete for an agent to reliably invoke the tool.

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

Parameters1/5

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

Schema coverage is only 25% (the description implicitly refers to 'assignments' but doesn't explain its structure). It fails to mention dry_run, groupIndex, trackIndex, or the nested locator/noteIndex fields. The example phonemes are given but the mapping to parameters is not explained, leaving the agent without enough guidance to construct a valid request.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: 'Directly assign formal SynthV space-separated phoneme strings to notes' with specific examples. It distinguishes itself from siblings like get_phonemes or set_note_attributes by focusing on phoneme assignment and the use case of MusicXML lyric joining.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The statement 'Solves MusicXML lyric joining issues' provides a clear use case. It implies when to use this tool (for lyric-related phoneme adjustments) without explicit comparison to alternatives, but the context is sufficient for most agents.

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