Skip to main content
Glama
Sign In

Wazza

by ai.wazza
OverviewDiscussionsAdmin

Complete an upload

complete_upload
Idempotent

Finishes an upload after the bytes are sent: checks them and makes the file ready for runs. For a multipart upload, give the parts with the ETag each PUT returned.

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": {
      "file_id": "<file_id>"
    },
    "name": "complete_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsNoMultipart uploads only: every part, numbered from 1, with its ETag.
file_idYesThe file id upload_file returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive behavior, and the description adds genuinely new context: it validates the uploaded bytes ('checks them') and performs a state transition to make the file usable by runs. It doesn't say what happens when validation fails or whether a failed completion leaves the upload resumable, which is the remaining gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with zero filler, front-loading the primary action and outcome before the conditional multipart instruction. Every clause carries information.

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 two-parameter, idempotent finalization tool with no output schema and full annotation coverage, the description supplies purpose, prerequisite stage, and conditional argument guidance. Only failure-mode behavior is left unstated, a minor omission given the tool's simplicity.

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?

Schema coverage is 100%, so both parameters are already documented, including the parts structure. The description still adds provenance the schema lacks: the etag must be the value each PUT returned, which clarifies how to populate the nested objects correctly.

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?

States a specific verb and resource ('Finishes an upload') plus the lifecycle position ('after the bytes are sent') and the outcome ('makes the file ready for runs'). An agent can distinguish it from upload_file 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 Guidelines4/5

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

The conditional for the optional parts argument is spelled out clearly ('For a multipart upload, give the parts with the ETag each PUT returned'), and the implicit sequencing after upload_file is evident from 'after the bytes are sent.' It stops short of explicit when-not-to-use guidance or naming a sibling alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Wazza toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources