Skip to main content
Glama

Rigged Clean

create_upload

Get a signed PUT for a local file. Run the upload command with the file itself, then pass upload_id to enhance_media. Upload exactly the declared byte count.

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

Input Schema

NameRequiredDescriptionDefault
filenameYes
size_bytesYes
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.

Output Schema

NameRequiredDescriptionDefault
curlYes
headersYes
upload_idYes
expires_atYes
upload_urlYes
anonymous_sessionNoKeyless session credential. Save the value returned on your first call and pass it on related calls and retries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, closed-world operation. The description adds real behavioral detail beyond that: the result is a signed PUT, the upload must match the declared byte count exactly, and the returned upload_id is the handoff token to enhance_media. It omits URL expiry and whether a retry creates a new upload, which are the main remaining unknowns.

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?

Three short sentences, front-loaded with the core action, then the workflow, then the hard constraint. No filler or restatement of the tool name.

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 values need not be explained, and annotations cover the safety profile. The description supplies the workflow and the byte-count constraint, which is enough to call it correctly. Minor gaps remain around signed-URL lifetime and retry behavior for a non-idempotent operation.

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 only 33% — only anonymous_session is documented in the schema. The description partially compensates by tying size_bytes to a hard constraint ('Upload exactly the declared byte count'), but filename is left entirely unexplained in both places. Baseline 3 is appropriate given the partial compensation.

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 states a specific verb and resource: 'Get a signed PUT for a local file.' It also names the downstream sibling enhance_media, so an agent can place the tool in a workflow. It stops short of a full 5 because it never explicitly contrasts this tool with any alternative way to get media in.

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?

It gives a clear sequence: call this, run the upload command with the file, then pass upload_id to enhance_media. That is actionable context for when to use it. It offers no exclusions or failure-path guidance (e.g., what to do if the PUT fails or the URL expires).

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