Skip to main content
Glama

kelpo_accept_shoot

Accept the whole multi-shot plan with ONE confirmation: debits every shot at once (atomic, all or nothing), queues them in parallel; the server then checks each shot, assembles and edits the video and delivers it in the conversation. Requires confirmed=true after the user approved the displayed total (max_credits = that total). Reuse the same idempotency_key after a timeout. A failed shot is refunded automatically. Same rights rule as generate (rights_confirmed). When kelpo_get_shoot lists english_directions_needed, send english (per shot number) or the call is refused before any charge. Arguments: {"path": {"id": "", "shoot_id": "<shoot_id>"}, "body": {"confirmed": true, "english": {}, "idempotency_key": "<idempotency_key>"}}

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_accept_shoot"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $defs / AcceptInput / properties / quality / description
      Previous value: -"Only when kelpo_get_shoot lists quality_options: \"hd\" when the person asked for HD. Omitted = Normal (the default)."New value: +"Only when kelpo_get_shoot lists quality_options: \"normal\" = Normal (the default when omitted), \"hd\" = HD, as the person chose."
    • addedInput schema / properties / body / type
      Added value: +"object"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: atomic all-or-nothing debit, parallel queuing, server-side per-shot validation, assembly and editing, delivery in the conversation, automatic refund of a failed shot, and refusal before any charge when `english` is missing. Annotations only carry the safety profile (readOnlyHint=false, destructiveHint=false), so this disclosure is where the real behavior comes from.

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 core action and confirmation rule, then preconditions, then failure/refund semantics. It is a dense single paragraph, and the trailing literal argument JSON largely restates the schema rather than earning its place.

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 explains the downstream pipeline, delivery location, refund behavior on partial failure, and the refusal path — enough for an agent to call it and interpret what happens next. It is silent on what the immediate response looks like (job id / status to poll with kelpo_get_job), which is the only material gap.

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?

Top-level schema description coverage is reported at 0% (path.id, path.shoot_id, confirmed, max_credits, idempotency_key are bare), so the description must carry the load. It does add meaning for confirmed (only after user-approved total), max_credits (equals the displayed total), idempotency_key (reuse after timeout), english (per shot number, gated by kelpo_get_shoot) and rights_confirmed (same rule as generate), but it never explains id vs shoot_id, which remain undocumented.

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 and resource ('Accept the whole multi-shot plan with ONE confirmation') and immediately distinguishes itself from the single-shot path by describing the all-at-once debit and parallel queueing. It does not explicitly name a sibling as the alternative, but the scope is unmistakable.

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?

Explicit preconditions and ordering: requires confirmed=true only after the user approved the displayed total, max_credits must equal that total, reuse the same idempotency_key after a timeout, and send `english` when kelpo_get_shoot lists english_directions_needed or the call is refused. It names the sibling (kelpo_get_shoot) that gates the call and the conditions under which it applies.

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