Skip to main content
Glama
Sign In

Spaces by Peakflo

by ai.peakflo
OverviewDiscussionsAdmin

file_get_upload_url

Get a one-time upload URL to push a local file into workflow storage — no JWT needed. On S3/GCS returns a presigned PUT URL (curl -X PUT). On local-storage returns a token-based POST URL on this server (curl -X POST -F file=@...). The response always includes a ready-to-run curlExample. After uploading, pass the returned storedPath as the file input to any workflow tool.

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

Input Schema

NameRequiredDescriptionDefault
fileNameYesOriginal filename, e.g. 'SOA as January 2026.pdf'
mimeTypeNoMIME type, e.g. 'application/pdf' or 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet'
expiresInSecondsNoURL TTL in seconds (default: 900; maximum: 3600)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the generic write-ish profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description goes well beyond that by disclosing backend-dependent behavior (S3/GCS presigned PUT vs. local token POST), that the URL is one-time, that no JWT is needed, and that a ready-to-run curlExample is always returned.

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?

Four tight sentences: purpose and auth exemption first, then the branching backend behavior with concrete curl invocations, then the return guarantee, then the follow-up step. Every sentence carries distinct information and nothing is repeated.

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, yet the description still tells the agent what comes back (a URL, a curlExample, and a storedPath) and how the different storage backends change the upload mechanics. Combined with 100% schema coverage, an agent has everything needed to call and then chain this tool.

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%, covering fileName, mimeType, and expiresInSeconds with examples and the TTL default/max, so the schema already does the heavy lifting. The description adds no parameter-level detail beyond referencing the output storedPath, so the baseline 3 applies.

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 one-time upload URL to push a local file into workflow storage') and names the artifact returned (presigned PUT URL vs. token-based POST URL). No sibling tool in the list handles file upload, and the description makes that unique role unambiguous.

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 clear when-to-use context — you have a local file and need it in workflow storage — and closes the loop by telling the agent to pass the returned storedPath as the `file` input to any workflow tool. It does not enumerate exclusions or say when not to use it, which keeps it just short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Spaces by Peakflo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources