Skip to main content
Glama

Get upload

get_upload
Read-only

The files the user added through a request_upload link. status is ready (use files[].id in a model's input slots or a studio tool), waiting (nothing uploaded yet: ask the user, do not poll in a loop) or expired (call request_upload again).

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": {
      "request_id": "<request_id>"
    },
    "name": "get_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds genuinely new context: the three lifecycle states and the explicit anti-pattern of polling in a loop while `waiting`. It does not mention whether state transitions are automatic or whether the result expires, but the state semantics cover the main behavioral risk.

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?

Tight and front-loaded: the resource is named first, then each status value is enumerated with its required action. No filler, though the opening sentence is a noun phrase rather than a direct statement of what the call does.

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?

An output schema exists, so return shape need not be explained, and the description instead covers the semantically important part — what each status means and what the agent should do next. Only the provenance/format of `request_id` is left implicit.

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?

There is one required parameter with 0% schema description coverage, so the description carries the burden; it implies `request_id` originates from a `request_upload` link but never states the format or where to obtain the value. That partial compensation keeps it at minimum-viable rather than weak.

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 identifies the resource precisely ('the files the user added through a `request_upload` link') and ties it to its sibling, so an agent knows this retrieves a pending upload request rather than a file listing. It lacks an explicit verb such as 'retrieve/check status of', so the read action is inferred from context and annotations rather than stated.

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?

Strong conditional guidance: use `files[].id` in model input slots or a studio tool when `ready`, ask the user and do not poll when `waiting`, and call `request_upload` again when `expired`. The only gap is that it never distinguishes this from `list_files` for an agent that wants already-uploaded files.

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