Skip to main content
Glama

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

Instrument catalog (the sound palette)

doseedo_instruments
Read-onlyIdempotent

The instrument list — the sound palette: every instrument doseedo can PLAY YOUR NOTES on (doseedo_render_midi) — orchestral strings, brass and winds, guitars, basses, keys, drums and percussion, and World instruments (koto, sitar, banjo, pedal steel, tabla, congas…). Each entry gives the EXACT render call (call: instrument, plus timbre_preset where one is needed — a koto is the acoustic_guitar model with the koto timbre), its playable range in concert MIDI pitch, whether it plays chords, its presets (pizz, muted, sax registers…) and a demo render. No args → the whole catalog; query:"warm low brass" / family / culture:"India" (a culture's own instruments: "Indian", "Japanese", "Celtic", "Latin America"…) / pitches:[…] (instruments whose range holds them) / chords:true narrow it; id:"cello" → one instrument in full. Read-only, free, no key needed — read it before writing a part.

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_instruments"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoOne instrument (id, alias or label, e.g. "cello", "upright bass", "koto") → its full entry: every preset with its own call and range, transposition, aliases, demo, page.
queryNoWhat the part needs, in words: an instrument ("trumpet"), a family ("woodwinds"), a technique ("pizzicato", "muted") or a register ("low", "bright"). Ranked best-first.
chordsNotrue = only instruments one player can play chords on.
familyNoOnly this family.
cultureNoOnly the instruments that are this culture's own sound — a culture ("India", "Japan", "Middle East", "Celtic", "Cuba", "Mexico", "Brazil", "Americana"…), a word for one ("Indian", "Carnatic", "Irish") or a region ("South Asia", "Latin America", "Europe"). The whole listing names every culture.
pitchesNoMIDI pitches the part uses (concert, 60 = C4) — only instruments whose range holds every one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / culture
      Added value: +{
      +  "description": "Only the instruments that are this culture's own sound — a culture (\"India\", \"Japan\", \"Middle East\", \"Celtic\", \"Cuba\", \"Mexico\", \"Brazil\", \"Americana\"…), a word for one (\"Indian\", \"Carnatic\", \"Irish\") or a region (\"South Asia\", \"Latin America\", \"Europe\"). The whole listing names every culture.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint and openWorldHint; the description adds the non-obvious operational facts "free, no key needed" and, importantly, what each entry contains (an exact render `call`, concert-MIDI range, chord capability, presets, demo). It slightly restates the read-only annotation, but the payload-structure disclosure is genuine added value.

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

Conciseness4/5

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

The purpose and the render_midi dependency are front-loaded, then parameter behavior follows in a readable progression from broad to narrow. It is a dense single paragraph with some enumerative filler (the long instrument-name lists) that could be trimmed, but nearly every clause carries information an agent would otherwise have to guess.

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 six-parameter, zero-required discovery tool with no output schema, the description covers coverage of all parameters, what a returned entry holds, the no-arg default, and the safety/cost profile. Nothing an agent needs in order to call it correctly or interpret the response 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 goes beyond the schema by showing how filters combine and by giving concrete query values ("warm low brass") and culture examples. It also clarifies the semantic difference between a broad `id` lookup returning one entry in full versus filter parameters that narrow the list — a distinction the schema alone leaves implicit.

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+resource — a catalog of every instrument doseedo can render MIDI on — and explicitly ties it to the sibling it feeds (doseedo_render_midi). The parenthetical examples (koto as acoustic_guitar model with koto timbre) make the resource concrete rather than abstract, so an agent can tell this apart from doseedo_recipes or doseedo_mix_preset without opening any 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?

It gives a clear imperative — "read it before writing a part" — and explains the browse-vs-narrow split (no args for the whole catalog, filters to narrow, id for one instrument in full). It does not explicitly exclude any scenario or name an alternative tool to prefer when, so it stops short of a full when/when-not treatment.

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