Skip to main content
Glama

kelpo_get_editing

Read-onlyIdempotent

Read selected sources, measured durations, version, plan, status and result_job_id. Poll this tool after render_editing; download the result with video_download. A failed render gives its montage credits back. 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_editing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description adds genuinely new context — that a failed render refunds montage credits and that the expected pattern is repeated polling. It omits polling cadence/termination and any auth or quota notes.

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?

Three short sentences, front-loaded with the return payload then workflow guidance, with no filler. The inline JSON argument blob is largely redundant with the schema and slightly interrupts the flow.

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, enumerating the returned fields in the description is the right call, and the poll-then-download lifecycle plus credit-refund behavior make it callable with confidence. Minor gaps remain around the id's origin and what a non-terminal status looks like.

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?

Only one nested parameter exists and schema coverage is 0%, so the description must compensate. It restates the shape ({"path": {"id": "<id>"}}) but never explains what the id refers to (an editing id from start_editing/finalize_editing) or where to obtain it, adding no real semantics beyond the schema.

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?

States a specific verb (read) plus the exact fields returned (sources, durations, version, plan, status, result_job_id), and ties itself to a concrete workflow position ('poll after render_editing'). An agent can distinguish it from siblings like kelpo_get_job or kelpo_preview_editing 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 Guidelines4/5

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

Explicitly says when to call it (poll after render_editing) and names the follow-up alternative (video_download for the result). It does not state exclusions such as when to use preview_editing or get_job instead, so it falls short of a 5.

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