Skip to main content
Glama

kelpo_get_music_clip

Read-onlyIdempotent

A music clip: status, the music (url to give the user once ready), its segments (one shot each: index, sung or dance, start/end in the song, singer and lines) with the shot you planned, missing_shots, the quote, the render progress and next = what to do now. Arguments: {"path": {"id": ""}}

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>"
    },
    "name": "kelpo_get_music_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely useful behavioral context — the returned URL is meant to be handed to the user once rendering completes, progress is surfaced, and missing_shots indicates incomplete planning — but it says nothing about behavior when the clip is not ready or invalid.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The field enumeration is dense but informative and front-loaded; the trailing literal 'Arguments' JSON block duplicates the input schema and earns no place. The single run-on sentence makes the segment sub-structure harder to parse than necessary.

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?

With no output schema, the description bears the full burden of describing the return value, and it does so thoroughly, including nested segment fields and the `next` pointer. The remaining gap is the unresolved `path.id` semantics and lack of error or not-ready behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter meaning and it does not: it merely restates the schema shape as {"path": {"id": "<id>"}} without explaining what the id identifies or where it comes from (e.g., the value returned by kelpo_create_music_clip).

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?

The description enumerates exactly what the resource is and exposes (status, music url, segments, shots, quote, render progress), which makes it clear this is a read of a music clip's state. However the retrieval verb is only implicit from the name, and it never distinguishes itself from siblings like kelpo_update_music_clip, kelpo_render_music_clip, or kelpo_get_job.

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

Usage Guidelines3/5

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

'url to give the user once ready' and '`next` = what to do now' imply the polling/state-check usage pattern without stating it as guidance. There is no explicit when-to-use or when-not-to-use instruction, and no named alternative for related lookups.

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