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

capture_audio

act imperative

The one tool that WAITS for a human to play: `waitForSignal: true` blocks up to `maxWaitSeconds` for the live output to rise above -60 dBFS, then measures the `captureSeconds` that follow. Left off, it reads the rolling 4 s buffer and returns at once, as analyze_audio({source:"recent"}) does. A window nobody played into comes back as `silent: true`. Offline renders bypass the live graph, so render_audio's output never appears here.

Input schema

Property	Type	Required	Description
`captureSeconds`	number	no	Window length, ending at the capture. Default 3, max 4 — the whole buffer.
`waitForSignal`	boolean	no	Wait for output above -60 dBFS, then capture `captureSeconds` from there. Default false: read the buffer and return at once.
`maxWaitSeconds`	number	no	Wait budget, default 5, capped at 10. Waiting in vain returns `signalDetected: false`, not an error.

Raw JSON schema

{
  "type": "object",
  "properties": {
    "captureSeconds": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 4,
      "description": "Window length, ending at the capture. Default 3, max 4 — the whole buffer."
    },
    "waitForSignal": {
      "type": "boolean",
      "description": "Wait for output above -60 dBFS, then capture `captureSeconds` from there. Default false: read the buffer and return at once."
    },
    "maxWaitSeconds": {
      "type": "number",
      "exclusiveMinimum": 0,
      "maximum": 10,
      "description": "Wait budget, default 5, capped at 10. Waiting in vain returns `signalDetected: false`, not an error."
    }
  },
  "additionalProperties": false
}