Skip to main content
Glama

Outil.io

Complete video upload

complete_video_upload

Assembler et vérifier les morceaux, puis créer le média. Une nouvelle invocation après succès retourne le même média.

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>"
    },
    "name": "complete_video_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description only needs to add behavior. It does add genuine value by disclosing idempotency ('a new invocation after success returns the same media'), which tells the agent retries are safe. However it says nothing about failure modes, chunk verification outcomes, or processing time, so it remains thin beyond the annotation baseline.

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?

Two short sentences with no filler, and the action sequence is front-loaded ahead of the retry caveat. Sizing is appropriate for a single-parameter finalization tool; the only weakness is that terseness shades into under-specification.

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?

With no output schema, no nested objects and only one required param, the tool is simple enough that a short description can suffice, and the idempotency note covers the most important runtime question. Still, it omits what the created media is (a video asset), what a failed verification returns, or whether the call blocks until assembly finishes.

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?

There is one parameter (uploadId, uuid) with 0% schema description coverage, and the description never mentions it. The parameter name is self-explanatory and required, so little is genuinely lost, but the description does not confirm that this ID must be the one issued by start_video_upload or explain the expected scope.

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 gives a specific verb sequence (assemble and verify the chunks, then create the media), which clearly identifies this as the finalization step of a chunked upload flow and separates it from siblings like upload_video_chunk and cancel_video_upload. It never names the media type (video asset) explicitly, but the tool name and title carry that.

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?

Usage is implied rather than stated: 'assemble the chunks, then create the media' positions it as the last step after chunks are uploaded, and the retry note hints it is safe to call again. There is no explicit when-not guidance, no mention of what precedes it by name, and no note about what happens if chunks are missing or incomplete.

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.