Skip to main content
Glama

kelpo_update_music_clip

Change a music clip before generating its music again: its lyrics (sections: ALL the sections again, in order), its English style, tempo, key, song length, title, language, cast or end card; only the fields sent change. Free; nothing is generated. Changing the lyrics, style, tempo, key, length, language or cast makes the current song out of date: its segments and planned shots are cleared and the clip is a draft again (then kelpo_generate_music). The title and end card alone keep the song and the shots. Not while a step is running. Use it after an error such as « the lyrics of section 4 were not recognized »: rewrite that section. Arguments: {"path": {"id": ""}, "body": {"version": 3}}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>",
      "body": "<body>"
    },
    "name": "kelpo_update_music_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, it discloses that only sent fields change, that the operation is free and generates nothing, and exactly which edits invalidate the song and clear segments/planned shots versus which keep them. It also gives a step-running guard. This is rich behavioral context not present in the annotation hints.

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?

It is dense but front-loaded, with each clause conveying a constraint or consequence. The trailing argument JSON example is somewhat redundant with the schema and slightly awkward, but the overall text is efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex nested mutation with no output schema, it covers usage, side effects, and invalidation well. It still omits what the required version represents or where to obtain it and what the call returns, leaving gaps for an agent to infer.

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?

Top-level schema coverage is 0%, so the description carries weight; it explains update semantics ('only fields sent change'), that sections must be supplied in full and in order, and which fields trigger invalidation. It does not explain the required version token or path id, so it is not perfect.

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 opens with a specific verb and resource ('Change a music clip') and enumerates the editable fields, making it clearly distinct from create/generate/render siblings.

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 states when to use (before regenerating, after a lyric-recognition error) and when not (while a step is running), and points to kelpo_generate_music as the follow-up. This is explicit routing rather than implied guidance.

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