Skip to main content
Glama

Doseedo Film Score: spot a video, play your score on AI instruments, mix it to picture

Polish a mix with a mix preset

doseedo_mix_preset

POLISH A MIX: a mix preset is a model trained on finished, professionally mixed recordings. It covers YOUR mix and folds what it hears back in by frequency range. preset: "cinematic_score" (the default) = a whole orchestral / film-score mix, the tone and width of a finished score moved onto yours, below 8 kHz, with none of the model's own audio heard. "jazz_mix" = the same for a JAZZ mix (a combo, bossa / latin jazz — what the jazz band generators play), trained on finished jazz records: use it for those in place of cinematic_score. "big_band_mix" = the same for a BIG BAND (saxes, trumpets, trombones and a rhythm section — what the big_band_* generators play), trained on big-band records alone: use it for a big band in place of jazz_mix. Input: audio_url (a doseedo_mix mix_url as returned) or audio_key, a stereo mix of up to 10 minutes. The preset brings its own strength; cns (0.1–0.5) overrides it: how much of your mix's own sound the model's take keeps (higher = closer to the input). Async: job_id → doseedo_wait_task (~15–90 s) → mix_url (the polished mix, WAV), take_url (the model's raw take) and report: balance_vs_input_db per band and side_vs_input_db (the width change). Cancel: the plane has no stop for a running mix preset — it runs to completion (credits spent), the job ends as canceled and its output is discarded. Only a job still queued at the plane is refunded by the plane's own failure refund.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "doseedo_mix_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnsNoThe model's strength over the preset's own: how much of the input's own sound its take keeps (0.1–0.5, higher = closer to the input).
nameNoOptional: a name for this job's files, e.g. "rainy-loop-3". Every file it returns downloads as <name>_<part>.<ext> (rainy-loop-3_Celesta.wav, rainy-loop-3_rough-mix.wav; one take: rainy-loop-3.wav), so the user can find them. Give each job its own name (a second take: "rainy-loop-3b"). Default: doseedo-<last 6 characters of the job id>.
seedNoOptional random seed (default 7).
presetNoThe mix preset: "cinematic_score" (default) — a whole orchestral / film-score mix; "jazz_mix" — a jazz mix (combo, bossa, latin jazz); "big_band_mix" — a big band.
audio_keyNoR2 ingest key of an uploaded audio file (from doseedo_get_upload_url / POST /api/upload/r2/ingest-url; starts with "ingest/").
audio_urlNohttps URL of the audio, as an alternative to audio_key: a doseedo result URL exactly as a job returned it (a stem, a take, a bounce), or any public URL. The gateway fetches it (≤256 MB) into your account's ingest storage before the job starts. Pass audio_key OR audio_url.
idempotency_keyNoOptional. Any unique string for THIS request (e.g. a UUID). Re-sending the same call with the same key after a timeout returns the same job instead of starting a second one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / preset / description
      Previous value: -"The mix preset: \"cinematic_score\" (default) — a whole orchestral / film-score mix; \"jazz_mix\" — a jazz mix (combo, big band, bossa, latin jazz)."New value: +"The mix preset: \"cinematic_score\" (default) — a whole orchestral / film-score mix; \"jazz_mix\" — a jazz mix (combo, bossa, latin jazz); \"big_band_mix\" — a big band."
  2. Changed1 schema field changed
    • changedInput schema / properties / preset / description
      Previous value: -"The mix preset: \"cinematic_score\" (default) — a whole orchestral / film-score mix."New value: +"The mix preset: \"cinematic_score\" (default) — a whole orchestral / film-score mix; \"jazz_mix\" — a jazz mix (combo, big band, bossa, latin jazz)."
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), the description discloses the full lifecycle: async job_id, ~15–90 s via doseedo_wait_task, three outputs (mix_url WAV, take_url raw model take, report with balance_vs_input_db per band and side_vs_input_db width change). It also discloses the cancellation semantics that the annotations do not cover — no stop exists, the job runs to completion and spends credits, its output is discarded, and only a job still queued gets the plane's failure refund.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content is front-loaded and every claim is substantive, but it is delivered as one dense block with inline quoted preset names, multi-clause sentences, and a mid-sentence switch from input to preset to cns to lifecycle. Splitting the preset catalogue and the async/refund behavior into their own lines would make the routing facts far easier to scan.

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?

With no output schema, the description carries the return-value burden and does: it names mix_url, take_url, and the shape of the report. For a 7-parameter, open-world, potentially credit-spending async tool, it covers inputs, model choice, timing, outputs, and the fact that cancellation cannot recover work — nothing an agent needs to call it correctly is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description still adds real meaning: it spells out what each preset is trained on and what it does to the mix (tone and width, below 8 kHz, none of the model's own audio heard), and it explains that cns overrides the preset's own strength with "higher = closer to the input". It also constrains input as a stereo mix of up to 10 minutes, which the schema does not state.

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?

Opens with a specific verb+resource ("POLISH A MIX") and immediately defines what a mix preset is: a model trained on finished, professionally mixed recordings that folds its own sense of the mix back into the input by frequency range. This is distinguishable from the sibling doseedo_mix and from the generators, so an agent can tell what the tool does 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?

The description gives unusually explicit preset-selection routing — jazz_mix "in place of cinematic_score" for a combo/bossa/latin jazz mix, big_band_mix "in place of jazz_mix" for a big band — plus the input alternative (audio_url vs audio_key) and the async handoff to doseedo_wait_task. The one gap is that it never states when to reach for this tool rather than the plain mix tool for the same material; the differentiation is implied by "polish" rather than asserted.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources