Skip to main content
Glama

Create upload links

create_upload

One-time URLs for uploading CPET files that are on disk, named by a path.

Returns an upload_url and a ready-to-run curl line. POSTing the file to it (multipart field file) returns the same summary as upload_cpet, cpet_id included. The bytes never enter the conversation, and the URL carries its own five-minute credential, so the command handles no API key.

curl -sS -F "file=@/path/to/export.csv" "<upload_url>"

For a folder, count mints every URL in one call (upload_urls), so one shell command can POST every file: a cohort takes two steps in total.

files=(/data/*.xls); urls=(URL1 URL2 ...)
for i in "${!files[@]}"; do
  curl -sS -F "file=@${files[$i]}" "${urls[$i]}"; done

Each URL accepts exactly one file, and they all expire five minutes after minting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many one-time URLs to mint, 1-200. Above 1 the result carries `upload_urls` as a list; `upload_url` is always the first.
filenameNoOnly used if the uploaded file carries no name of its own.
retain_hoursNoHours to keep the parsed record beyond the 24 h default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / count / description
      Added value: +"How many one-time URLs to mint, 1-200. Above 1 the result carries `upload_urls` as a list; `upload_url` is always the first."
    • addedInput schema / properties / filename / description
      Added value: +"Only used if the uploaded file carries no name of its own."
    • addedInput schema / properties / retain_hours / description
      Added value: +"Hours to keep the parsed record beyond the 24 h default."
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses key behavior: each URL is one-time and expires five minutes after minting, carries its own credential so no API key is handled, and accepts exactly one file. It also explains the multipart field name, the return fields upload_url and upload_urls, and how count changes the response shape.

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?

The description is front-loaded with purpose, return values, and constraints, followed by useful curl examples. It is somewhat long because of the two code blocks, but the examples serve a real operational purpose; a little trimming of the folder example could tighten it further.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-value burden and does so by naming upload_url, upload_urls, and cpet_id. It also covers expiry, one-file-per-URL limits, embedded credentials, folder batching, and the equivalent summary from upload_cpet, leaving no important behavioral gap for calling the tool correctly.

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 the input schema already documents count, filename, and retain_hours thoroughly. The description reinforces count behavior with the upload_urls example but adds little semantic detail about filename or retain_hours beyond what the schema states, matching the baseline for fully covered parameters.

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?

The description states a specific resource and scope: one-time upload URLs for CPET files that live on disk and are named by path. It also distinguishes the result from upload_cpet by noting that POSTing to the URL returns the same summary, including cpet_id, so an agent can tell what this tool does and how it relates to the sibling.

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?

The description gives clear context for when this tool is appropriate: files are on disk, bytes should not enter the conversation, and folders can be handled with count to mint every URL in one call. It references upload_cpet as producing the same summary, but it does not explicitly say when to prefer upload_cpet over create_upload or state exclusions.

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