Skip to main content
Glama

kelpo_generate_music

Generate (or generate again) the song of a music clip on Kelpo's GPU. confirmed=false: price in credits and balance; confirmed=true with max_credits = that price: charged now, ready in a few minutes (follow kelpo_get_music_clip), refunded if it fails. Generating again replaces the song and its segments (the planned shots are cleared). 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_generate_music"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior2/5

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

The description adds genuinely valuable behavior beyond the annotations: immediate charging, refund on failure, a few-minute turnaround, and that regeneration replaces the song and clears planned shots. However, that last disclosure contradicts the supplied destructiveHint=false, which would tell an agent it is safe to re-run without losing plan data; because the annotations and prose disagree on a consequential side effect, reliance on either is undermined.

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?

Content is front-loaded (purpose first, then the confirmation protocol, then the replacement caveat) and the inline argument example is compact and useful. It is dense, packing cost, timing, refund, follow-up and side effects into a single compound sentence with nested parentheses, but little of it is 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 charge-incurring, nested-payload mutation with no output schema, the description covers cost, confirmation gating, timing, refunds, polling target and regeneration effects. The remaining gap is the two unexplained optional body fields and any mention of how the priced quote is returned, but an agent could call it correctly from what is stated.

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?

With 0% reported schema description coverage, the description carries the burden and does explain the crucial semantics of confirmed and max_credits (price-then-charge coupling), plus a concrete argument example. It says nothing about idempotency_key or rights_confirmed, leaving those body fields undocumented in both the schema and the prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Generate (or generate again) the song of a music clip on Kelpo's GPU" gives a specific verb, resource and execution venue, and clarifies that it covers regeneration as well as first generation. It stops short of distinguishing this from adjacent siblings such as kelpo_create_music_clip or kelpo_render_music_clip, which an agent could plausibly confuse with it.

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?

The description spells out the exact calling protocol: call with confirmed=false first to receive the credit price and balance, then call again with confirmed=true and max_credits equal to that price to actually charge and start generation. It also names the follow-up tool (kelpo_get_music_clip) and warns that regenerating replaces the existing song, which is precisely the when/when-not guidance an agent needs.

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