modularsynth-mcp

Overview Schema Source Related Servers Discussions Admin

Set notes

set_notes

Destructive

Writes or replaces notes on one page (A–D) of a Note Grid sequencer, defining each note’s start step, length, MIDI pitch, and optional velocity for verse or chorus patterns.

Instructions

Write the notes of one page (A–D, default A) of a Note Grid sequencer; the other pages are kept. Each note: start step (0–63: sixteenth notes when clocked by Clock ×4, thirty-second notes when the Note Grid "resolution" setting is 1), length in steps, MIDI pitch (60 = C4), optional velocity. Replaces the notes of that page. Only the page selected by the "page" setting plays: put a verse on A and a chorus on B, then save scenes with different "page" values.

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": {
      "id": "<id>",
      "notes": "<notes>"
    },
    "name": "set_notes"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`page`	No
`notes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1Nov 2, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds valuable specifics beyond that – it says exactly what is destroyed ('Replaces the notes of that page') and what survives ('the other pages are kept'). It omits auth requirements or response behavior, but the destruction scope is well disclosed.

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?

Front-loaded with the core action and reasonably dense; every sentence carries information. The timing aside about Clock ×4 is a bit parenthetical but still useful, and there is no 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?

For a 3-parameter mutation tool with no output schema, the description covers the page-selection model, note encoding, and destructive scope well enough to call it correctly. The only gaps are the 'id' parameter and the return/response behavior.

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

Parameters4/5

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

With 0% schema coverage, the description compensates substantially: it explains the page enum, the timing meaning of 'start' (sixteenth vs thirty-second notes depending on resolution), length in steps, pitch with 60=C4, and optional velocity. It does not describe the 'id' parameter or the 256-note limit, so it is not fully complete.

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?

States a specific verb and resource ('Write the notes of one page ... of a Note Grid sequencer') with clear scope: default page A and other pages preserved. An agent can distinguish this write-notes operation from play_notes or set_param without opening the schema.

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?

Gives concrete usage context (put a verse on A and a chorus on B, then save scenes with different page values) and clarifies default page behavior. It stops short of explicitly naming alternatives or exclusions, but the intended scenario is clear.

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