Skip to main content
Glama

Create an upload

create_upload

For a local file bigger than 8 MB: returns a one-time upload URL and a curl command. Run the command in a shell (files over 95 MB need parts, see partBytes), then call convert with the returned uploadId. The slot expires after an hour.

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": {
      "fileName": "<fileName>"
    },
    "name": "create_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNameYesThe file name with its extension
sizeBytesNoThe file size, if known

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare the mutation/idempotency profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the description carries real weight here and does: one-time URL, expiry after an hour, external shell execution required, and a size-tiered flow. It stops short of saying what happens if the slot expires or whether re-invoking mints a fresh slot, which matters for a non-idempotent tool.

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 tight sentences with the precondition front-loaded and the follow-up call at the end, which matches the order an agent needs them. The only drag is the dangling 'see partBytes' reference, which costs a moment of confusion.

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?

There is no output schema, and the description compensates well by naming the returned artifacts (upload URL, curl command, uploadId) and their lifetime. Gaps remain around the multi-part path and failure/expiry recovery, but the core call sequence is complete.

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 coverage is 100%, so fileName and sizeBytes are already documented in the schema; the description only implies sizeBytes via the 8 MB and 95 MB thresholds and says nothing about fileName. Baseline 3 is appropriate since the schema does the heavy lifting.

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 action and return payload: it issues a one-time upload URL plus a curl command for a local file above 8 MB. The 8 MB precondition immediately separates it from the sibling 'convert' path, so an agent can pick the right tool without reading further.

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?

Gives an explicit entry condition (>8 MB local file) and the exact follow-up sequence: run the shell command, then call convert with the returned uploadId. It also flags the >95 MB multi-part branch, though that branch points at 'partBytes', which is not a parameter in the schema, leaving the agent unsure how to act on the guidance.

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.