Skip to main content
Glama

add_notes

Add lyrics with timing and pitch to vocal tracks in Synthesizer V AI Vocal Studio for creating or editing vocal melodies.

Instructions

Add one or more notes to a track

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
trackIdYesID of the track
notesYesArray of notes to add

Implementation Reference

  • MCP CallToolRequestSchema handler case for 'add_notes': validates and sanitizes input (trackId as number, notes array non-empty, map to string/number), calls executeCommand('add_notes'), returns formatted text response or error.
    case "add_notes": {
      const args = request.params.arguments as any;
      const trackId = Number(args.trackId);
    
      if (isNaN(trackId)) {
        return {
          content: [{
            type: "text",
            text: "Error: Invalid track ID"
          }],
          isError: true
        };
      }
    
      if (!Array.isArray(args.notes) || args.notes.length === 0) {
        return {
          content: [{
            type: "text",
            text: "Error: No notes provided"
          }],
          isError: true
        };
      }
    
      const result = await executeCommand("add_notes", {
        trackId,
        notes: args.notes.map((note: any) => ({
          lyrics: String(note.lyrics),
          startTime: Number(note.startTime),
          duration: Number(note.duration),
          pitch: Number(note.pitch)
        }))
      });
    
      if (result.error) {
        return {
          content: [{
            type: "text",
            text: `Error: ${result.error}`
          }],
          isError: true
        };
      }
    
      return {
        content: [{
          type: "text",
          text: result.message || `${args.notes.length} notes added successfully`
        }]
      };
    }
  • Tool definition including name, description, and inputSchema for 'add_notes' returned by ListToolsRequestSchema handler (serves as registration). Defines required trackId (string) and notes array of objects with lyrics, startTime, duration, pitch.
    name: "add_notes",
    description: "Add one or more notes to a track",
    inputSchema: {
      type: "object",
      properties: {
        trackId: {
          type: "string",
          description: "ID of the track"
        },
        notes: {
          type: "array",
          description: "Array of notes to add",
          items: {
            type: "object",
            properties: {
              lyrics: {
                type: "string",
                description: "Lyrics text for the note"
              },
              startTime: {
                type: "number",
                description: "Start time in ticks"
              },
              duration: {
                type: "number",
                description: "Duration in ticks"
              },
              pitch: {
                type: "number",
                description: "MIDI pitch (0-127)"
              }
            },
            required: ["lyrics", "startTime", "duration", "pitch"]
          }
        }
      },
      required: ["trackId", "notes"]
    }
  • Generic helper function invoked by the add_notes handler to dispatch the command to Synthesizer V Studio by writing JSON {action: 'add_notes', trackId, notes} to COMMAND_FILE and polling RESPONSE_FILE for result.
    async function executeCommand(action: string, params: any = {}): Promise<any> {
      const command = {
        action,
        ...params
      };
    
      await writeCommand(command);
      return await readResponse();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action ('Add') but lacks critical behavioral details: whether this is a mutation (implied), permission requirements, idempotency, error handling (e.g., invalid trackId), or effects on existing notes. For a write operation with zero annotation coverage, this is a significant gap.

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 a single, efficient sentence with zero waste. It front-loads the core purpose ('Add one or more notes to a track') without unnecessary elaboration, making it easy to parse.

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 tool's complexity (mutation with nested array parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects, return values, or usage context, leaving the agent under-informed for safe and effective invocation.

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%, so the schema fully documents both parameters (trackId and notes array with its nested properties). The description adds no additional meaning beyond implying the notes are added to the specified track, aligning with the baseline for high schema coverage.

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 clearly states the action ('Add') and target ('notes to a track'), specifying it can handle 'one or more notes'. It distinguishes from siblings like 'edit_notes' (modification) and 'get_track_notes' (retrieval), but doesn't explicitly contrast with 'add_track' (which creates tracks rather than adding notes).

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 guidance on when to use this tool versus alternatives like 'edit_notes' or 'add_track'. The description implies usage for adding notes to existing tracks but doesn't mention prerequisites (e.g., track must exist), exclusions, or contextual cues for selection among siblings.

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/ocadaruma/mcp-svstudio'

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