Skip to main content
Glama

kelpo_finalize_editing

Idempotent

Save an existing preview after explicit user approval (confirmed=true). Supply the editing version and optionally the chosen preview job_id. No re-render; saving costs get_editing montage_price (its credits) unless this version was already rendered. Sharing remains a separate explicit decision. Arguments: {"path": {"id": ""}, "body": {"version": 3, "confirmed": true}}

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_finalize_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

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations: it discloses that saving is not a re-render, that it debits get_editing montage_price unless the version was already rendered, and that sharing is separate. Those are exactly the cost and side-effect facts annotations cannot express. It is consistent with readOnlyHint=false, destructiveHint=false and idempotentHint=true ('unless this version was already 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 precondition, then cost, then the sharing caveat — every prose sentence earns its place. The trailing 'Arguments: {...}' JSON blob largely restates the schema and is the one wasteful element.

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 nested-body mutation with no output schema and no annotation detail on cost, it covers the essentials: approval gate, which version, optional preview job, no re-render, credit cost, and the sharing boundary. What is missing is what the tool returns and what the path id identifies.

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% schema description coverage the description has to carry all param meaning. It does explain version (required), job_id (optional, the chosen preview) and confirmed (=true), but path.id is never described and job_id's 32-hex format is omitted. Partial compensation only.

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?

States a specific verb+resource ('Save an existing preview'), and by saying 'No re-render' it implicitly separates itself from kelpo_preview_editing and kelpo_get_editing. It stops short of naming a sibling or an alternative outright, so an agent must infer the boundary rather than read it.

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?

Gives a clear precondition ('after explicit user approval (confirmed=true)') and clarifies that sharing 'remains a separate explicit decision', which tells the agent not to conflate finalization with publishing. No explicit when-not or named alternative, so not 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