Skip to main content
Glama

kelpo_render_music_clip

Render the music clip (every shot in HD, lip-sync on the song, dance shots, end card, assembly). confirmed=false: quote (video seconds at the HD price + assembly) and what is missing; confirmed=true with max_credits = that quote (and rights_confirmed=true only after the user declared their rights on the photos/logo and the agreement of the people shown) → ONE video job, follow it with kelpo_get_job; refunded if the clip cannot be made. After a delivery, when only the end card or the title changed (kelpo_update_music_clip), the quote says reassembly: the shots already made are reused and nothing is generated (free like any re-edit, within a daily limit). Arguments: {"path": {"id": ""}, "body": {"confirmed": true, "max_credits": 1}}

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

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare non-read-only, non-destructive, but the description goes well beyond them: credit quoting, refund on failure, reuse of already-rendered shots for reassembly, and a daily free-re-edit limit are all disclosed. The one gap is the idempotency_key parameter, which is never explained even though the annotation says idempotentHint=false — the agent gets no guidance on whether and when to supply it.

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?

Every clause carries operational information and the primary action is front-loaded, but the single dense paragraph of nested parentheses and conditional arrows is harder to parse than a short bulleted flow. The trailing literal `Arguments:` JSON restates the schema and is the weakest use of space, though it does usefully illustrate a valid confirmed call.

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 credit-consuming mutation with nested input and no output schema, the description supplies the critical missing pieces: refund policy, the follow-up call that yields the result, and the reassembly economics. What remains thin is the exact shape of the quote response (how 'what is missing' is expressed) and the size of the daily re-edit limit.

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 description coverage is 0%, so the description carries the load, and it does define confirmed (quote vs. render), max_credits (must equal the quoted amount) and rights_confirmed (only after the user declares rights on photos/logo and consent of depicted people) in a way the bare schema does not. Only idempotency_key is left undefined in both places, so the compensation is strong but not total.

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?

Opens with a specific verb and resource ('Render the music clip') and enumerates exactly what the deliverable contains: HD shots, lip-sync on the song, dance shots, end card, assembly. It also distinguishes itself from the sibling kelpo_update_music_clip by scoping that tool to end-card/title-only changes, so an agent can route without opening the schema.

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?

Gives an explicit two-phase protocol: confirmed=false returns a quote plus what is missing; confirmed=true with max_credits matching the quote starts exactly one job, which must then be followed with kelpo_get_job. It also names the alternative path after a delivery (end card/title only → kelpo_update_music_clip with `reassembly`) and calls out the rights_confirmed precondition, covering when-not as well as when.

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