Skip to main content
Glama
Sign In

Doseedo: Film Scoring, AI Instruments, Sound Effects & Stems

by com.doseedo
OverviewDiscussionsAdmin

Check a job

doseedo_check_task
Read-onlyIdempotent

Check an async doseedo task once. Returns current status, and the result (file URLs / notes) when finished. A big result comes back as a brief (each row cut to its deciding fields): parts: ["" or index, …] returns those rows of the job record IN FULL — a render_score part's every receipt, a mix part's strip, rides (every point) and loudness.

Input Schema

NameRequiredDescriptionDefault
kindNoWhich job kind created the task — the registry name the submit reply carried (generate_music, generate_sound, cover_stem, fill_gap, render_midi, train_instrument, render_score, mix, session_from_stems, spot_video, score_to_picture, reframe_video, cover_song, separate_stems, split_soundtrack, transcribe, audio_to_session, convert_project, bounce_session, analyze_song, detect_chords, beat_grid, check_take, analyze_midi); the short codes (generate, sound, coverstem, fillgap, render, train, score, stemsess, spot, picture, reframe, cover, separate, soundtrack, session, convert, bounce, analyze, chords, beats, check, harmony) are accepted aliases.
partsNoOptional, on a finished job: the parts to return in full, by name (as the result names them) or index — e.g. ["Oboes", "Timpani"].
job_idNoAlternatively the job_id (job_…) from a submit tool or the jobs API — replaces task_id + kind.
task_idNoThe task_id returned by a submit tool.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"Which job kind created the task — the registry name the submit reply carried (generate_music, generate_sound, cover_stem, fill_gap, render_midi, train_instrument, render_score, mix, session_from_stems, spot_video, score_to_picture, cover_song, separate_stems, split_soundtrack, transcribe, audio_to_session, convert_project, bounce_session, analyze_song, detect_chords, beat_grid, check_take, analyze_midi); the short codes (generate, sound, coverstem, fillgap, render, train, score, stemsess, spot, picture, cover, separate, soundtrack, session, convert, bounce, analyze, chords, beats, check, harmony) are accepted aliases."New value: +"Which job kind created the task — the registry name the submit reply carried (generate_music, generate_sound, cover_stem, fill_gap, render_midi, train_instrument, render_score, mix, session_from_stems, spot_video, score_to_picture, reframe_video, cover_song, separate_stems, split_soundtrack, transcribe, audio_to_session, convert_project, bounce_session, analyze_song, detect_chords, beat_grid, check_take, analyze_midi); the short codes (generate, sound, coverstem, fillgap, render, train, score, stemsess, spot, picture, reframe, cover, separate, soundtrack, session, convert, bounce, analyze, chords, beats, check, harmony) are accepted aliases."
    • changedInput schema / properties / kind / enum
      Previous value: -[
-  "generate_music",
-  "generate_sound",
-  "cover_stem",
-  "fill_gap",
-  "render_midi",
-  "train_instrument",
-  "render_score",
-  "mix",
-  "session_from_stems",
-  "spot_video",
-  "score_to_picture",
-  "cover_song",
-  "separate_stems",
-  "split_soundtrack",
-  "transcribe",
-  "audio_to_session",
-  "convert_project",
-  "bounce_session",
-  "analyze_song",
-  "detect_chords",
-  "beat_grid",
-  "check_take",
-  "analyze_midi",
-  "generate",
-  "sound",
-  "coverstem",
-  "fillgap",
-  "render",
-  "train",
-  "score",
-  "stemsess",
-  "spot",
-  "picture",
-  "cover",
-  "separate",
-  "soundtrack",
-  "session",
-  "convert",
-  "bounce",
-  "analyze",
-  "chords",
-  "beats",
-  "check",
-  "harmony"
-]New value: +[
+  "generate_music",
+  "generate_sound",
+  "cover_stem",
+  "fill_gap",
+  "render_midi",
+  "train_instrument",
+  "render_score",
+  "mix",
+  "session_from_stems",
+  "spot_video",
+  "score_to_picture",
+  "reframe_video",
+  "cover_song",
+  "separate_stems",
+  "split_soundtrack",
+  "transcribe",
+  "audio_to_session",
+  "convert_project",
+  "bounce_session",
+  "analyze_song",
+  "detect_chords",
+  "beat_grid",
+  "check_take",
+  "analyze_midi",
+  "generate",
+  "sound",
+  "coverstem",
+  "fillgap",
+  "render",
+  "train",
+  "score",
+  "stemsess",
+  "spot",
+  "picture",
+  "reframe",
+  "cover",
+  "separate",
+  "soundtrack",
+  "session",
+  "convert",
+  "bounce",
+  "analyze",
+  "chords",
+  "beats",
+  "check",
+  "harmony"
+]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, open-world), and the description adds genuinely non-obvious behavior: large results are truncated to a 'brief' with rows cut to deciding fields, and specifying parts expands them. It does not mention error/failed states or whether the task record persists after completion.

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 core purpose is front-loaded in the first sentence, but the second sentence is a dense run-on packed with unexplained domain jargon ('a mix part's strip, rides (every point) and loudness') that costs more parsing effort than it returns.

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 4-parameter read-only check tool with no output schema, the description covers the return shape and the brief/full-result dichotomy well. The main gap is the absence of failure-state handling and any statement that either job_id or task_id+kind is needed, which the agent must infer from annotations and schema.

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

Parameters3/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. The description mostly restates what the schema says ('parts returns those rows IN FULL', job_id replacing task_id + kind), though it does add some meaning by explaining what 'full' entails for render_score and mix parts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 ('Check an async doseedo task once') plus what the reply contains (status, result file URLs/notes). The word 'once' implicitly contrasts with the polling/blocking sibling doseedo_wait_task, but it never names that sibling, so the differentiation is inferential rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: you check a task returned by a submit tool, repeatedly if polling. There is no explicit when-to-use versus doseedo_wait_task or doseedo_list_jobs, and no guidance on retry cadence or what to do on a failed status.

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

All Doseedo: Film Scoring, AI Instruments, Sound Effects & Stems toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources