Skip to main content
Glama
N0zoM1z0

VOCALOID MCP

by N0zoM1z0

Create Canonical Song Manifest

vocaloid_create_song_manifest

Creates a revisioned canonical song manifest with detailed musical structure (sections, tempos, keys, chords). Enables building VSQX or WAV artifacts later through the build workflow.

Instructions

Create the revisioned canonical song manifest; derive VSQX/WAV artifacts later through the build workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesFilename-safe song slug used in all derived artifact names
titleYes
chorusNo
formatNovsq3
reverbNo
temposNo
song_idYesGlobally unique stable lowercase ID; preserve it across unrelated revisions
sectionsYesOrdered, non-overlapping semantic song sections
overwriteNo
key_changesNo
output_pathYesNew .song.json path
pre_measureNo
sample_rateNo
chord_changesNo
soundfont_pathNoAbsolute path, or a path relative to the vocaloid-mcp-server project root
response_formatNomarkdown
time_signaturesNo
accompaniment_gainNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataYes
warningsYes
Behavior2/5

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

Annotations provide no hints (all false), and the description only states 'create', implying mutation but no further behavioral traits like idempotency, scope, or side effects. For a creation tool, more disclosure is needed.

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 description is a single efficient sentence with no wasted words. It front-loads the core action, though it could benefit from slightly more detail.

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?

The tool has 18 parameters, complex nested schemas, and an output format (response_format parameter), yet the description explains none of this. It fails to define what a 'canonical song manifest' is or how to use the output.

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 only 28%, yet the tool description adds no additional context for parameters. It does not compensate for the low coverage, leaving many parameters (like 'song_id', 'sections', etc.) with only schema constraints.

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 it creates a canonical song manifest and mentions deriving artifacts later, clearly indicating the tool's primary function. However, it does not explicitly distinguish from siblings like 'vocaloid_build_song_manifest' beyond the workflow hint.

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?

No usage guidelines provided; no indication of when to use this tool vs alternatives (e.g., build workflow or inspect), and no prerequisites or exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/N0zoM1z0/vocaloid-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server