cosynth.vercel.app WebMCP Tools, Schemas & Agent Capabilities

← WebMCP Directory

cosynth.vercel.app

live Unverified (seed import) AI & Agents 24 tools imperative implementation

Open website How verification works

A synthesizer you control by talking to AI.

First seen 2026-11-05 · Last seen 2026-11-05 · Source: webmcp.com

Answer 8 · Act 14 · Transact 2 · Score: Not yet scored

Tool inspector

set_fx_order

transact imperative May require confirmation

Reorder the effects chain — the one patch edit with no parameter behind it, so until now an agent could switch every effect on without being able to say which came first. `order` is all 8 effect ids exactly once, first processed first; whether an effect does anything is ` .enabled` in update_parameters. Example: {"order":["fxdist","chorus","phaser","flanger","delay","reverb","eq","comp"]}

Input schema

Property	Type	Required	Description
`order`	array	yes	All 8 effect ids exactly once, in processing order (default chorus, phaser, flanger, delay, reverb, eq, comp, fxdist). A missing, repeated or unknown id is an error, not a partial reorder.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "order": {
      "type": "array",
      "minItems": 8,
      "maxItems": 8,
      "items": {
        "type": "string",
        "enum": [
          "chorus",
          "phaser",
          "flanger",
          "delay",
          "reverb",
          "eq",
          "comp",
          "fxdist"
        ]
      },
      "description": "All 8 effect ids exactly once, in processing order (default chorus, phaser, flanger, delay, reverb, eq, comp, fxdist). A missing, repeated or unknown id is an error, not a partial reorder."
    }
  },
  "required": [
    "order"
  ],
  "additionalProperties": false
}