Skip to main content
Glama

edit_notes

Modify note properties like lyrics, timing, and pitch in Synthesizer V AI vocal tracks to adjust vocal performances.

Instructions

Edit one or more notes

Input Schema

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

Implementation Reference

  • Handler for the 'edit_notes' MCP tool. Validates trackId and notes array, maps note properties to numbers/strings, executes the 'edit_notes' command via file-based IPC to Synthesizer V Studio Lua script, and returns success message or error.
    case "edit_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("edit_notes", {
        trackId,
        notes: args.notes.map((note: any) => ({
          id: Number(note.id),
          lyrics: note.lyrics && String(note.lyrics),
          startTime: note.startTime && Number(note.startTime),
          duration: note.duration && Number(note.duration),
          pitch: note.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 edited successfully`
        }]
      };
    }
  • src/index.ts:331-373 (registration)
    Registration of the 'edit_notes' tool in the ListToolsRequestSchema handler, including name, description, and detailed input schema defining trackId and array of notes with required id and optional lyrics, startTime, duration, pitch.
      name: "edit_notes",
      description: "Edit one or more notes",
      inputSchema: {
        type: "object",
        properties: {
          trackId: {
            type: "string",
            description: "ID of the track"
          },
          notes: {
            type: "array",
            description: "Array of notes to edit",
            items: {
              type: "object",
              properties: {
                id: {
                  type: "number",
                  description: "The ID of the note"
                },
                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: ["id"]
            }
          }
        },
        required: ["trackId", "notes"]
      }
    },
  • Generic helper function used by all tools, including 'edit_notes', to serialize command to JSON file and poll for response from Synthesizer V Studio Lua script.
    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?

With no annotations provided, the description carries full burden but only states the action ('edit') without disclosing behavioral traits such as permissions needed, whether edits are destructive or reversible, error handling, or rate limits. It doesn't add context beyond the basic operation.

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's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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 of editing multiple notes with nested properties, no annotations, and no output schema, the description is incomplete. It doesn't address what the tool returns, error conditions, or how edits are applied, leaving significant gaps for a mutation 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%, so the schema fully documents parameters (trackId and notes array with nested properties). The description adds no meaning beyond this, as it doesn't explain parameter relationships or usage nuances. Baseline 3 is appropriate when schema does the heavy lifting.

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

Purpose3/5

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

The description 'Edit one or more notes' states the action (edit) and resource (notes), but it's vague about scope and doesn't distinguish from sibling tools like 'add_notes' or 'get_track_notes'. It lacks specificity about what 'edit' entails (e.g., updating lyrics, timing, pitch).

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 is provided on when to use this tool versus alternatives like 'add_notes' for creating new notes or 'get_track_notes' for retrieval. The description implies usage for editing existing notes but doesn't specify prerequisites (e.g., note IDs must exist) 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/ocadaruma/mcp-svstudio'

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