Skip to main content
Glama
Sign In
svs-mcp

svs-mcp

by tatat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_phonemes

Check the phonemes actually used for synthesis for each note in a group, including user overrides, to verify pronunciation before or after edits. Retry if the converter is still running.

Instructions

Get the phonemes actually used for synthesis for every note in a group (SV's text-to-phoneme output), alongside any user overrides. Useful to check pronunciation before or after edits. If complete is false the converter was still running — retry after a moment.

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": {
      "track": "<track>"
    },
    "name": "get_phonemes"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoGroup index within the track (see get_project_info `groups`). Defaults to the first non-main group — in SV Studio 2 the singer is attached per group and notes in the main group are not synthesized.
trackYesTrack index, 1-based

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the asynchronous converter behavior via the `complete` flag and advises retrying, which adds meaningful context. It does not explicitly state read-only nature, but the verb 'Get' implies it.

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?

The description is three sentences, front-loaded with the core purpose, followed by a use case and a vital async note. Every sentence earns its place with no redundancy or filler.

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

Completeness4/5

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

Given no output schema, the description sufficiently covers the return scope (phonemes plus overrides) and the important `complete` flag behavior. It also situates the tool's use case. It could be more exhaustive about exact return shape, but it is complete enough for a focused getter tool.

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 description coverage is 100% for both parameters, including detailed descriptions for `group` (default behavior and SV Studio 2 nuance) and `track` (1-based). The description adds no parameter-specific details beyond the schema, so the baseline score of 3 applies.

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 tool gets the phonemes used for synthesis for every note in a group, specifically SV's text-to-phoneme output alongside user overrides. This distinguishes it from sibling tools like set_phonemes and get_notes with a specific verb and resource.

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?

Provides a clear use case ('Useful to check pronunciation before or after edits') that conveys when to use the tool. It does not explicitly name alternatives or state when-not to use it, but the context is sufficient for an agent to recognize its purpose relative to siblings.

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

Deploy Server

Other Tools