Skip to main content
Glama

kelpo_generate

Create one approved video and return its job ID. Requires confirmed=true after explicit price approval (quote_id and max_credits from the quote; prices are in credits). The answer carries credits (balance, videos_5s_left, low, expires_next, buy_url, message to relay to the user). Without enough credits: 402 detail.code=credits_required with the 3 packs and buy_url; Kelpo never buys credits by itself. If the quote/requirements list rights_confirmation_required, pass rights_confirmed=true only after the user explicitly declared their rights on those files and the agreement of the people shown or recorded; already declared files need nothing. A refusal returns detail.code (rights_confirmation_required with asset_ids, terms_acceptance_required with action_url). Reuse the same idempotency_key and quote_id after a timeout; never announce a launch from an error response. Arguments: {"path": {"id": ""}, "body": {"confirmed": true, "english": "", "idempotency_key": "<idempotency_key>", "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_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $defs / GenerateInput / properties / quality / description
      Previous value: -"Only when the quote lists quality_options: \"hd\" when the person asked for HD. Omitted = Normal (the default)."New value: +"Only when the quote 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.8/5.0
Behavior5/5

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

Annotations only say the call is non-read-only and not inherently idempotent; the description adds the real behavioral contract: 402 detail.code=credits_required with the three packs and buy_url, refusal codes (rights_confirmation_required with asset_ids, terms_acceptance_required with action_url), and the warning never to announce a launch from an error response. This is materially more than the annotations convey.

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 the confirmation requirement, and every sentence carries operational detail (error codes, retry policy, rights gate). It is dense and error-code-heavy in one run-on block, which costs a little readability, but nothing is redundant.

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?

Despite there being no output schema, the description explains what the answer carries (credits balance, videos_5s_left, low, expires_next, buy_url) and enumerates the failure paths an agent must handle. For a paid, destructive-adjacent creation call with a nested body, this is complete enough to act on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Top-level schema coverage is 0%, so the description carries weight: it explains that confirmed and max_credits must come from an approved quote, that quote_id must be reused on retry, and when rights_confirmed is legitimate. It does not cover quality, ai_label, resolution or max_charge_cents, though those have their own in-schema descriptions.

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?

"Create one approved video and return its job ID" gives a specific verb, resource and return value, and the word "approved" separates it from the quoting/planning siblings (kelpo_quote_scene, kelpo_preview_editing). An agent can tell this is the final paid render step without consulting the schema.

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: confirmed=true only after explicit price approval with quote_id and max_credits from the quote; rights_confirmed=true only after the user declares rights; retry with the same idempotency_key after a timeout. It also states an exclusion — Kelpo never buys credits itself — and names what does not count (assets.consent, record_exchange).

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