Skip to main content
Glama

kelpo_request_reference_upload

Idempotent

Prepare a private 15-minute image/audio upload (50 MiB max); no video uploads as chat or editing references (a video only with role swap_source, for kelpo_swap_person). Send bytes with a local HTTP tool, not through the LLM/MCP context, then complete_reference_upload. Same idempotency key + metadata returns the same ticket; changed metadata is rejected. Rights are confirmed before generation. Arguments: {"body": {"filename": "photo.jpg", "size_bytes": 123456, "mime_type": "image/jpeg", "sha256": "<64 hex>", "idempotency_key": "", "role": "unassigned", "project_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": {
      "body": "<body>"
    },
    "name": "kelpo_request_reference_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / ReferenceUploadInput / properties / idempotency_key / minLength
      Previous value: -8New value: +3
  2. Changed4 schema fields changed
    • changedInput schema / $defs / ReferenceUploadInput / properties / mime_type / description
      Previous value: -"Actual image or audio MIME, e.g. audio/ogg. image/svg+xml only for a logo (role unassigned or visual), where offered: it becomes a sharp PNG. No videos."New value: +"Actual image or audio MIME, e.g. audio/ogg. image/svg+xml only for a logo (role unassigned or visual), where offered: it becomes a sharp PNG. Videos (video/mp4, video/quicktime, video/webm) only with role swap_source; never as chat references."
    • changedInput schema / $defs / ReferenceUploadInput / properties / role / description
      Previous value: -""New value: +"swap_source = a video (4 to 15 s, 95 MB, MP4/MOV/WebM) whose person is replaced by an actor with kelpo_swap_person."
    • changedInput schema / $defs / ReferenceUploadInput / properties / role / enum
      Previous value: -[
      -  "unassigned",
      -  "identity",
      -  "environment",
      -  "product",
      -  "voice",
      -  "sound",
      -  "visual",
      -  "wardrobe"
      -]New value: +[
      +  "unassigned",
      +  "identity",
      +  "environment",
      +  "product",
      +  "voice",
      +  "sound",
      +  "visual",
      +  "wardrobe",
      +  "swap_source"
      +]
    • changedInput schema / $defs / ReferenceUploadInput / properties / size_bytes / description
      Previous value: -"50 MiB max."New value: +"50 MiB max (95 MiB for a swap_source video)."
  3. Changed4 schema fields changed
    • changedInput schema / $defs / ReferenceUploadInput / properties / mime_type / description
      Previous value: -"Actual image or audio MIME, e.g. audio/ogg. image/svg+xml only for a logo (role unassigned or visual), where offered: it becomes a sharp PNG. Videos (video/mp4, video/quicktime, video/webm) only with role swap_source; never as chat references."New value: +"Actual image or audio MIME, e.g. audio/ogg. image/svg+xml only for a logo (role unassigned or visual), where offered: it becomes a sharp PNG. No videos."
    • changedInput schema / $defs / ReferenceUploadInput / properties / role / description
      Previous value: -"swap_source = a video (4 to 15 s, 95 MB, MP4/MOV/WebM) whose person is replaced by an actor with kelpo_swap_person."New value: +""
    • changedInput schema / $defs / ReferenceUploadInput / properties / role / enum
      Previous value: -[
      -  "unassigned",
      -  "identity",
      -  "environment",
      -  "product",
      -  "voice",
      -  "sound",
      -  "visual",
      -  "wardrobe",
      -  "swap_source"
      -]New value: +[
      +  "unassigned",
      +  "identity",
      +  "environment",
      +  "product",
      +  "voice",
      +  "sound",
      +  "visual",
      +  "wardrobe"
      +]
    • changedInput schema / $defs / ReferenceUploadInput / properties / size_bytes / description
      Previous value: -"50 MiB max (95 MiB for a swap_source video)."New value: +"50 MiB max."
  4. Changed1 schema field changed
    • addedInput schema / properties / body / type
      Added value: +"object"
  5. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (idempotentHint, destructiveHint=false), the description adds real operational behavior: a 15-minute ticket lifetime, idempotency semantics including rejection when metadata changes with the same key, a transport requirement that bytes bypass the MCP context, and the consent/rights timing before generation. These are exactly the facts an agent needs and none are recoverable from the annotations.

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?

It is front-loaded with purpose, size limit, and video exclusion before the transport and idempotency notes, and every clause carries information. It reads as one dense run-on paragraph, and the trailing example JSON partly repeats what the nested schema already declares.

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 multi-step upload flow with no output schema, it covers the two-step handshake, transport rule, TTL, and idempotency conflict behavior. It stops short of describing what the returned ticket actually contains (upload URL/expiry fields) and leaves the consent and rights-confirmation mechanics implicit relative to the parameters that carry them.

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 registers as 0% (the only top-level property is 'body'), and the inline example argument supplies useful shape for the required fields (filename, size_bytes, mime_type, sha256, idempotency_key, role, project_id). However, it omits and does not explain consent, person/person_id, identity_people, use_as_dialogue, reusable, or client_id, and it never enumerates the non-swap role values, so it only partially compensates for the coverage gap.

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?

The description gives a specific verb+resource — 'Prepare a private 15-minute image/audio upload (50 MiB max)' — plus the exact scope (a ticket that is later completed) and hard limits. It also explicitly carves out the sibling use case (video only with role swap_source for kelpo_swap_person), so an agent can distinguish it from kelpo_complete_reference_upload and kelpo_swap_person without opening any 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?

It states when to use it and what to do next ('Send bytes with a local HTTP tool, not through the LLM/MCP context, then complete_reference_upload'), and it names the exclusion (no video chat/editing references) with the one qualifying alternative. The sequencing constraint is explicit rather than inferred.

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