Skip to main content
Glama

files_complete_upload

Finish an upload started with files_create_upload_url, after the bytes have been PUT to the upload_url.

Verifies the object actually landed and matches the size (and sha256, when one was declared), then makes the file usable: from here file_id works in messages_send, messages_send_email attachments, documents.create, and the rest.

A file over 100 MB is stored only: it can be sent, downloaded or passed on by file_id, but its contents are not indexed for search (indexed: false).

Returns: file_id, status, byte_size, mime_type, indexed (on the call that completes the upload).

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": "files_complete_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_idYesfile_id returned by files_create_upload_url
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false. The description adds real behavior: it verifies the object landed and matches declared size and sha256, it transitions the file into a usable state, and it discloses the 100 MB threshold where `indexed: false` — a non-obvious consequence no annotation conveys.

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?

Front-loaded with the action and its prerequisite, then verification, then the large-file caveat, then the return values. Every sentence carries distinct information; the only mild softness is the vague "and the rest" when listing downstream consumers.

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?

No output schema exists, and the description compensates by enumerating the return fields (file_id, status, byte_size, mime_type, indexed) and noting which call surfaces them. Verification behavior, the size threshold, and downstream usability are all covered for a two-parameter tool.

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 100%, with file_id documented as "file_id returned by files_create_upload_url" and in_workspace fully explained. The description restates the file_id provenance but adds no syntax, format, or constraint beyond the schema, and never mentions in_workspace, so the baseline 3 applies.

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?

Names a specific verb and resource ("Finish an upload") and pins it to the preceding step ("started with files_create_upload_url, after the bytes have been PUT"), which cleanly separates it from files_create_upload_url and files_upload. An agent can place this tool in the workflow 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 prerequisite ordering is explicit: create the URL, PUT the bytes, then call this. It also names downstream consumers (messages_send, messages_send_email, documents.create) so the agent knows why completing matters. It stops short of an explicit exclusion such as "use files_upload instead for one-shot uploads," which is the only remaining gap.

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.