Skip to main content
Glama

kelpo_preview_editing

Idempotent

Render the current edit as a private provisional video in the same conversation, without generation credits. Poll get_editing for status preview and result_job_id. More changes may follow; only finalize_editing saves a reviewed video in My videos. 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_preview_editing"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), and the description adds real context on top: no credit consumption, the output is private/provisional and scoped to the same conversation, and how to retrieve the result. What's missing is cost/latency or limits on how many previews can be rendered.

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?

Front-loaded with the action and its distinguishing property, then the follow-up, then the exclusion. Four short sentences with no filler; the trailing raw JSON argument blob is slightly awkward as prose but is compact and useful.

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?

No output schema exists, yet the description tells the agent how to obtain the result (poll get_editing, watch result_job_id) and where the artifact does not live (not in My videos). Combined with the explicit finalize step, this is enough to run the preview→review→finalize loop without guessing.

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?

Schema description coverage is 0% and the two parameters are nested, so the description has to carry the load. The inline example conveys the shape ({path:{id}, body:{version}}), but it never explains what `version` means (edit version to snapshot? expected version for concurrency?) beyond assigning it the literal 3. Shape is clarified; semantics are not.

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 and resource ('Render the current edit as a private provisional video') plus the key property that sets it apart from siblings: it costs no generation credits and does not save anything. The reader immediately knows this is the preview step, not the commit step.

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?

Names the follow-up tool explicitly ('Poll get_editing for status preview and result_job_id') and the exclusion explicitly ('only finalize_editing saves a reviewed video in My videos'). The condition for using the alternative is also given ('More changes may follow'), so the agent can choose correctly between preview and finalize.

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