Skip to main content
Glama

Request upload

request_upload

Get a link where the user can upload files from their device (a photo of themselves, a product image, a clip, a voice track).

    Use this whenever the user refers to a file you cannot give a
    public URL for, including anything they attached to this chat:
    attachments cannot be passed to Affogato. Show the user
    `upload_url` as a clickable link and ask them to tell you when they
    are done, then call `get_upload` with `request_id` for the file ids.
    `purpose` is shown on the page: say what to upload ("A clear photo
    of your face"). `kind` is image, video, audio or any. The link
    works for one hour and only for a signed-in member of this
    workspace. Costs no credits.

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": {
      "purpose": "<purpose>"
    },
    "name": "request_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoany
purposeYes
max_filesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: the link expires after one hour, is scoped to a signed-in member of this workspace, and costs no credits. It also prescribes the agent's user-facing behavior (show upload_url as a clickable link, ask the user to confirm completion). Nothing here contradicts readOnlyHint=false or openWorldHint=false.

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?

Front-loaded with purpose, then usage, then the call sequence, then per-parameter notes. The parenthetical list of example file types is slightly redundant but each paragraph advances a distinct point; only max_files wastes a sentence's worth of omission.

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?

Covers the full request-then-poll workflow, the return field to surface (upload_url), and the handoff parameter (request_id), which is more than an agent needs to use it correctly; the output schema can cover return values. Only max_files is undocumented, which is minor for a low-stakes link-generating tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden. It explains that purpose is user-visible on the page (with an example), and names the accepted kind values (image, video, audio, any) that the schema does not enumerate. max_files is left completely unexplained, which is the one real gap.

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 ('Get a link where the user can upload files from their device') and enumerates the media it covers (photo, product image, clip, voice track). It is clearly distinguishable from get_upload and upload_file, which are named in the workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it ('whenever the user refers to a file you cannot give a public URL for, including anything they attached to this chat') and why attachments cannot be used directly. It also gives the follow-up condition and the sibling to call next (get_upload with request_id).

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