Skip to main content
Glama

sound_effects

Idempotent

Control automatic sound effects for a film or shot by setting volume, room tone, per-event sounds, custom audio files, and resets.

Instructions

Dinoctor's automatic sound effects (from the style's sound pack, worked out from what happens in each shot). Film-wide: on, volume, room tone. One shot: shot_on, shot_volume, and one sound by its event key: event_on, pick another sound, own_path (the person's own file), gain, nudge, reset. Call with just shot to list that shot's sounds and their event keys (no change). One undo step per change. For music use music; for any other sound file use upload as sound.

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": "sound_effects"
  }
}

Input Schema

NameRequiredDescriptionDefault
onNoFilm-wide: sound effects on or off.
gainNoThat sound's volume in dB.
pickNoAnother sound from that event's choices.
roomNoFilm-wide: quiet room tone under everything.
shotNoA shot id. With only this, lists the shot's sounds.
eventNoOne sound's event key, from the list.
nudgeNoFrames earlier (-) or later (+).
resetNotrue: that sound back to automatic.
volumeNoFilm-wide volume in dB, -18 to 6.
shot_onNoThis shot's sound effects on or off.
event_onNoThat sound on or off.
own_pathNoFull path of the person's own sound file to use for that event.
shot_volumeNoThis shot's volume in dB.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.1.2
    • addedInput schema / properties / event / description
      Added value: +"One sound's event key, from the list."
    • addedInput schema / properties / event_on / description
      Added value: +"That sound on or off."
    • addedInput schema / properties / gain / description
      Added value: +"That sound's volume in dB."
    • addedInput schema / properties / nudge / description
      Added value: +"Frames earlier (-) or later (+)."
    • addedInput schema / properties / on / description
      Added value: +"Film-wide: sound effects on or off."
    • addedInput schema / properties / own_path / description
      Added value: +"Full path of the person's own sound file to use for that event."
    • addedInput schema / properties / pick / description
      Added value: +"Another sound from that event's choices."
    • addedInput schema / properties / reset / description
      Added value: +"true: that sound back to automatic."
    • addedInput schema / properties / room / description
      Added value: +"Film-wide: quiet room tone under everything."
    • addedInput schema / properties / shot / description
      Added value: +"A shot id. With only this, lists the shot's sounds."
    • addedInput schema / properties / shot_on / description
      Added value: +"This shot's sound effects on or off."
    • addedInput schema / properties / shot_volume / description
      Added value: +"This shot's volume in dB."
    • addedInput schema / properties / volume / description
      Added value: +"Film-wide volume in dB, -18 to 6."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, idempotent, non-destructive mutation. The description adds value by revealing that each change is one undo step and that a shot-only call performs no mutation. It doesn't cover permission requirements or what the mutating response returns, but the annotation layer covers the safety profile.

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?

Front-loaded with purpose, then scope tiers, then alternatives, with no filler sentences. The telegraphic style ("One shot: shot_on, shot_volume, and one sound by its event key") is dense but still parseable; a slightly clearer separation of the three tiers would help.

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 13-parameter mutation tool with no output schema, the definition covers what is changed, at which scope, how to enumerate valid event keys, and the undo footprint. It stops short of describing failure modes (e.g., an invalid event key or own_path) but nothing essential for a correct call 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 parameter meaning is already documented; the description goes further by grouping the 13 params into film-wide (on, volume, room), per-shot (shot_on, shot_volume), and per-event (event_on, pick, own_path, gain, nudge, reset) tiers. That grouping, plus the shot-only listing semantics, is meaning the schema alone does not convey.

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 names the specific resource and its scope: "Dinoctor's automatic sound effects (from the style's sound pack, worked out from what happens in each shot)," plus the film-wide and per-shot scopes. It distinguishes itself from siblings by naming both alternatives: "For music use music; for any other sound file use upload as sound."

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

Usage Guidelines5/5

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

It gives explicit routing rules: music goes to music, other sound files to upload as sound. It also states a concrete no-op mode ("Call with just shot to list that shot's sounds and their event keys (no change)"), so an agent knows how to inspect before mutating.

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