Skip to main content
Glama

Outil.io

Upload video chunk

upload_video_chunk

Envoyer un morceau base64 d’un import ouvert. index commence à 0 ; taille exactement chunkSize sauf le dernier. Peut remplacer le même morceau avant assemblage.

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": {
      "uploadId": "<uploadId>",
      "index": "<index>",
      "base64": "<base64>"
    },
    "name": "upload_video_chunk"
  }
}

Input Schema

NameRequiredDescriptionDefault
indexYes
base64Yes
uploadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds genuinely useful behavior beyond that: chunk replacement is permitted before assembly and index is zero-based. It does not say whether re-uploading costs quota or how many retries are tolerated.

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?

Three short clauses, front-loaded with the action, then the two constraints. Semi-colon packing is dense but readable. No filler.

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

Completeness3/5

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

For a three-parameter streaming write with no output schema and no annotation detail beyond hints, the essentials are present but several things an agent needs are absent: the source of chunkSize, the maximum index, and what occurs after the last chunk is accepted.

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?

Schema description coverage is 0%, so the description must carry the load: it explains that 'base64' is a raw chunk payload, that 'index' starts at 0, and that size must equal chunkSize except for the final chunk. However, it never identifies where chunkSize comes from, does not mention the schema's 0-31 index bound, and does not explain the relationship between uploadId and the open import.

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?

The description names a specific action and resource: sending a base64 chunk belonging to an already-open import. It distinguishes the tool from upload-completion siblings by framing it as one piece of an in-progress import, though it never names the start/complete tools it depends on.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'd'un import ouvert' implies the precondition that an upload must already be started, which is real guidance but only implicit. There is no explicit statement of when the flow ends, which sibling to call after the last chunk, or what to do on failure.

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.