Skip to main content
Glama

Upload file

upload_file

Import a public http(s) image, video or audio URL into the workspace and get a file id to pass in a model's input slots. For a file with no public URL (a chat attachment, something on the user's device) use request_upload instead.

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": {
      "url": "<url>"
    },
    "name": "upload_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
filenameNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description is consistent with fetching remote content. It adds useful context beyond the annotations: the input must be a public URL and the result is a file id for model input slots. It does not mention size/format limits, fetch failures, or processing latency, which would be valuable for an ingest operation.

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 tight sentences: the primary purpose and outcome come first, the alternative second. No redundant restatement of the name or title, no filler.

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?

The presence of an output schema means return values need not be explained, and the sibling routing is complete. However, for an upload tool with zero schema coverage, the definition omits the `filename` parameter's meaning and any constraints on size, supported formats, or failure behavior.

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 0%, so the description must compensate. It adds real meaning for `url` (must be public, http(s), and one of image/video/audio), but says nothing about `filename` — whether it overrides the derived name or is optional metadata. That leaves one of two parameters undocumented everywhere.

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 ('Import') and resource (a public http(s) image/video/audio URL) plus the outcome (a file id usable in a model's input slots). This clearly separates it from request_upload, which handles non-public sources.

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 names the condition that selects the sibling tool: files with no public URL (chat attachments, local device files) should use `request_upload` instead. The positive case ('public http(s) URL') and the exclusion are both stated, leaving nothing to inference.

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