Skip to main content
Glama

music

Idempotent

Add a background track beneath voice, set its volume and ducking depth, or remove it with one undo step. Returns the track settings.

Instructions

The film's background music: add the person's music file (it's levelled so it sits under the voice; the levelled copy replaces it by itself a minute or two later), set its volume and how far it drops under the voice, or remove it. One undo step. Returns the music settings. For short sounds at a moment, use upload as sound or sound_effects.

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

Input Schema

NameRequiredDescriptionDefault
duckNoHow far it drops under the voice, dB 0 to 24. Default 12.
gainNoVolume in dB, -24 to 6.
nameNoA name for it. Default: the file name.
pathNoFull path of a music file on this computer.
removeNotrue: remove the music.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.2
    • addedInput schema / properties / duck / description
      Added value: +"How far it drops under the voice, dB 0 to 24. Default 12."
    • addedInput schema / properties / gain / description
      Added value: +"Volume in dB, -24 to 6."
    • addedInput schema / properties / name / description
      Added value: +"A name for it. Default: the file name."
    • addedInput schema / properties / path / description
      Added value: +"Full path of a music file on this computer."
    • addedInput schema / properties / remove / description
      Added value: +"true: remove the music."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare the safety profile (not read-only, idempotent, non-destructive), and the description adds real behavior: levelling happens asynchronously ('the levelled copy replaces it by itself a minute or two later'), the change costs 'One undo step', and the call returns the music settings. These are non-obvious traits an agent would otherwise have to discover by trial.

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 operation list is front-loaded and every sentence carries information. The long parenthetical about levelling is dense and slightly interrupts the sentence flow, but it is not filler.

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 five-parameter mutation tool with annotations and no output schema, the definition covers the operation set, the undo cost, the async levelling side effect, and the return value. It lacks nothing critical, though the interaction between repeated adds and the existing track is left implicit.

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 description coverage is 100%, so gain, duck, name, path and remove are already fully documented, including the same 'how far it drops under the voice' phrasing used in the description. The description adds only the framing that the file gets levelled, which is context rather than parameter guidance.

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 ('The film's background music') and the exact operations: add the person's music file, set its volume/ducking, or remove it. It is clearly distinguishable from the sibling 'sound_effects' and 'upload' tools, which it explicitly routes short sounds to.

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 an explicit alternative for a different case: 'For short sounds at a moment, use upload as sound or sound_effects.' That is clear routing, but it doesn't address when to use the dedicated 'remove' sibling instead of the remove flag, nor any prerequisite for adding music.

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