Skip to main content
Glama

Prepare file uploads

create_file_picker_uploads

Reserve temporary upload URLs for files selected in the upload picker. Use the picker’s workspace and each file’s exact byte length. Upload the raw bytes before verifying completion. Returns one upload_id and its PUT instructions per file.

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": {
      "workspace_id": "<workspace_id>",
      "files": "<files>"
    },
    "name": "create_file_picker_uploads"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYesLocal files to stage, described by their filenames, exact byte lengths, and MIME types when known. Their combined size must not exceed 256 MiB.
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics.
workspace_idYesDestination selected when opening the file picker. Pass that workspace's ID, or null when the picker targets the personal workspace.

Output Schema

NameRequiredDescriptionDefault
uploadsYesOne upload reservation for each requested file.
message_for_assistantNoContext, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare not read-only, not idempotent, not destructive, so the agent knows state is created. The description adds meaningful behavior: URLs are temporary, one upload_id plus PUT instructions are returned per file, and raw bytes must be PUT before verification. It does not mention URL expiry or retry behavior, which keeps it below a 5.

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?

Four short sentences, front-loaded with what is reserved and followed by the operation order. No filler, no restatement of the title.

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?

Output schema covers return values, and the description still summarizes them briefly; parameter coverage is complete. Minor gaps remain around the file-count and combined-size limits and what happens if the PUT is never performed, but nothing critical to a correct call is missing.

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 workspace_id, byte_length, content_type, and files are already fully documented. The description reinforces that workspace comes from the picker and byte length must be exact, but adds no syntax or constraint detail beyond the schema; 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?

States a specific verb and resource ('Reserve temporary upload URLs for files selected in the upload picker') and implicitly distinguishes itself from the verify step by noting bytes must be uploaded 'before verifying completion'. An agent can tell this is the staging step in a two-phase upload flow.

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 clear sequencing context (reserve, then upload raw bytes, then verify) and tells the caller to use the picker's workspace and exact byte length. It does not explicitly name verify_file_picker_uploads as the next tool, so routing relies on the phrase 'before verifying completion' rather than a named alternative.

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.

Resources