Skip to main content
Glama

prepare_upload

Creates a direct upload target for a named file and size, with optional SHA-256 for instant upload; use another HTTP-capable tool to send the file bytes.

Instructions

Create a direct upload target. Optional SHA-256 enables instant upload; bytes must be sent by the agent using another HTTP-capable tool.

Input Schema

NameRequiredDescriptionDefault
nameYestarget file name
sizeYesfile size in bytes
sha256Nooptional lowercase SHA-256; enables instant upload
parent_idNodestination folder UUID; omit for root
transportNoauto, single_put, or multipart
parent_pathNoabsolute parent folder path instead of parent_id
content_typeNoMIME type
idempotency_keyNostable retry key, maximum 128 characters

Output Schema

NameRequiredDescriptionDefault
modeYes
nodeNo
sha256No
statusYes
failureNo
put_urlNo
part_sizeNo
part_urlsNo
upload_idNo
expires_atNo
total_partsNo
uploaded_partsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The description adds meaningful behavior beyond the annotations: this tool creates an upload target, does not transmit file bytes itself, and SHA-256 can enable instant upload. It does not contradict destructiveHint=false. It still omits operational details such as upload expiry, auth requirements, or lifecycle expectations, so a 4 is appropriate.

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 short sentences with no wasted wording. The core action is front-loaded, followed by the critical operational note about SHA-256 and external byte transmission.

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?

An output schema exists, so return values need not be explained. The description captures the key non-obvious behavior that this tool prepares but does not perform the upload. For a complex multi-step upload workflow, however, it does not explain finalization with complete_upload, abort behavior, or multipart coordination.

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%, so the parameters are fully documented in the schema. The description repeats the SHA-256 instant-upload behavior already stated in the schema and adds no further parameter guidance. The baseline 3 applies.

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 states a specific verb and resource: 'Create a direct upload target.' It also clarifies that this tool only prepares the upload rather than sending bytes. It does not explicitly distinguish itself from sibling tools like complete_upload or get_upload_parts, so it falls short of a 5.

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?

The description gives an important usage constraint: the agent must send bytes with another HTTP-capable tool. It also mentions the optional SHA-256 shortcut. However, it does not say when to choose this over alternatives, nor does it explain the required follow-up flow with complete_upload or related tools.

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