Skip to main content
Glama

kelpo_start_editing

Idempotent

Prepare editing within any existing conversation. Original videos are preserved. Read get_editing for its separate version. 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_start_editing"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already state readOnly=false, destructive=false and idempotent=true, so the safety profile is largely covered. The description adds two genuine pieces of context beyond that: the operation targets an existing conversation (a prerequisite) and original videos are preserved (a side-effect guarantee). It still omits what state the tool produces and whether the editing session persists.

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?

It is short and the purpose sentence leads, which is good. But one of the three sentences is a literal restatement of the input schema, which earns no place in a description and crowds out the semantics it should have provided.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a non-read-only state-changing tool with no output schema and a completely undocumented nested parameter. The description never says what the caller gets back, what becomes editable, or how a subsequent kelpo_apply_operations/kelpo_finalize_editing relates to it, leaving the agent guessing on a mutation.

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% and the single parameter is a nested object, so the description must carry the load. Instead it just echoes the JSON shape with "Arguments: {"path": {"id": "<id>"}}", never saying whether id is a conversation id, project id, or shoot id, or what a "path" means here.

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

Purpose3/5

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

"Prepare editing within any existing conversation" gives a verb and a rough resource, but "editing" and "conversation" are domain terms never defined, and the agent cannot tell whether this creates an editing session, unlocks one, or stages assets. It does at least distinguish itself from kelpo_get_editing by naming that sibling.

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

Usage Guidelines2/5

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

"Read get_editing for its separate version" points at one alternative but is a documentation-navigation hint rather than a when-to-use rule. Nothing says when to call this instead of kelpo_finalize_editing, kelpo_select_editing_sources, or kelpo_update_editing_plan, nor what precondition (an existing conversation) must hold.

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