Skip to main content
Glama

kelpo_answer_offer

Answer the fix offer of a delivered multi-shot video: decision=accept (confirmed=true, after the user approved the offer's credits; regenerates ONLY the listed shots, then re-assembles and re-edits automatically; the previous version stays in Mes vidéos) or decision=decline (the video is kept as is). Arguments: {"path": {"id": "", "shoot_id": "<shoot_id>"}, "body": {"decision": ""}}

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

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/5.0
Behavior4/5

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

Annotations only declare the generic profile (not read-only, not destructive, not idempotent, closed-world). The description adds real, non-redundant behavior: only the listed shots are regenerated, assembly and editing are re-run automatically, and the previous version is preserved in Mes vidéos, plus a credit-approval precondition. It does not mention the idempotency_key affordance or expected failure modes, so 4 rather than 5.

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?

The outcome of each decision is front-loaded before the argument skeleton, and no sentence is wasted. The inline JSON-ish argument sketch with hard line breaks is a bit clunky, but the overall length is proportionate to the tool's complexity.

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

Completeness5/5

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

For a credit-consuming mutation with a deeply nested payload and no output schema, the description delivers what an agent needs to decide and call: both branches, the credit-approval gate, the regeneration scope, and the safety net of keeping the old version. The nested English direction semantics are fully documented in the schema $defs, so no gap remains in the description itself.

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 coverage is effectively 0% (path and body carry no descriptions), and the description compensates partially by spelling out the path/body envelope and the meaning of decision and confirmed. It says nothing about offer_id, max_credits, idempotency_key, resolution, or the large nested english/EnglishDirections payload, which the $defs document instead — so the description only partly fills the gap.

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 ('answer the fix offer of a delivered multi-shot video') and immediately enumerates the two possible decisions with their consequences. It is concrete enough to act on, but it never names or contrasts the sibling tools (e.g. kelpo_retake_shoot, which also redoes shots), leaving a real risk of selecting the wrong one.

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 gives the condition for each branch: accept after the user approved the offer's credits, decline keeps the video as is, and confirmed=true is a hard gate for accept. It lacks any 'when not to use' or alternative routing (e.g. what to call if there is no pending offer), so it stops 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