modularsynth-mcp

Overview Schema Source Related Servers Discussions Admin

Set bypass

set_bypass

Bypass or re-enable a synth module without unplugging it: effects pass input through, while sources and modulators go silent, helping isolate parts of a rich patch.

Instructions

Bypass a module (on: true) or turn it back on (on: false), without unplugging anything: effects and processors (filters, VCA, mixers, delay, reverb…) pass their input straight through; sources and modulators (oscillators, LFO, envelopes, sequencers, clock…) go silent. Output, Scope and Memo can’t be bypassed. Useful to hear a part of a rich patch more clearly; the user can undo it.

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>",
      "on": "<on>"
    },
    "name": "set_bypass"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`on`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.4.0Nov 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, it explains exactly what happens: effects and processors pass input through, while sources and modulators go silent. It also lists unbypassable module types and confirms undoability, matching the non-destructive annotation and giving rich behavioral context.

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 definition is dense but well organized: core bypass semantics and the on mapping come first, followed by effects/sources behavior, exclusions, and usage context. Every clause carries useful information and nothing is wasted.

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

Completeness5/5

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

For a simple two-parameter mutation tool with no output schema, the description covers purpose, parameter semantics, affected module categories, exceptions, and usage context. The only minor gap is how to source module ids, which is likely covered by sibling tools like describe_patch.

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 description coverage, the description compensates by explaining the critical boolean semantics: on=true bypasses, on=false restores. It also implies id identifies the target module, though it does not specify the id format or how to obtain module ids.

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 states a specific verb and resource: bypass a module or turn it back on. It distinguishes the operation from unplugging or removing modules and names the modules that cannot be bypassed, so an agent can tell it apart from siblings like remove_module or disconnect.

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?

It gives a clear use case ('hear a part of a rich patch more clearly') and notes that the user can undo it, which points to the undo sibling. It also states exclusions (Output, Scope, Memo), though it does not explicitly compare against alternatives such as set_param or disconnect.

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