Skip to main content
Glama

Developer Utilities & Validators (Tanod)

upload_file_get_link

utilpeek: Upload a file and get a download link that expires in 24 hours. Returns a public download link to a file you upload, valid for ttl_hours (default 24, the most); every call stores a new copy under a new link. Over HTTP the file may also be the raw request body or a multipart file part. PDF, Office, ODF, image, audio, CSV, JSON, text and Markdown only, up to 20 MB, detected from the bytes (HTML, SVG, scripts, executables and archives are a 415, not charged). Anyone with the link can download until it expires; Report abuse to support@tanod.dev; links expire within 24 hours. Typically under 1 s. Price: USD 0.005. No free tier. Docs: https://tanod.dev/learn/upload-file-get-link-for-agents.html

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

Input Schema

NameRequiredDescriptionDefault
filenameYesFile name with its extension, such as report.pdf. The extension is not trusted: the type is detected from the bytes. It sets the name in the link.
ttl_hoursNoHours the link stays valid, 1-24 (default 24, the most).
content_base64YesThe file, base64 encoded, up to 20 MB decoded. Allowed: PDF, DOCX, XLSX, PPTX, ODT, ODS, ODP, PNG, JPEG, WebP, GIF, TIFF, BMP, MP3, WAV, M4A/MP4 audio, OGG, FLAC, CSV, JSON, TXT, Markdown. HTML, SVG, scripts, executables and archives are refused with 415.

Output Schema

NameRequiredDescriptionDefault
urlNo
nameNo
bytesNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
sha256No
expires_atNo
output_noteNo
content_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / content_base64 / title
      Removed value: -"Content Base64"
    • removedInput schema / properties / filename / title
      Removed value: -"Filename"
    • removedInput schema / properties / ttl_hours / title
      Removed value: -"Ttl Hours"
    • removedInput schema / title
      Removed value: -"upload_file_get_linkArguments"
    • removedOutput schema / properties / content_type / description
      Removed value: -"Detected from the file's bytes, not from the name you sent."
    • removedOutput schema / properties / expires_at / description
      Removed value: -"UTC time the link stops working (within 24 hours)."
    • removedOutput schema / properties / name / description
      Removed value: -"The file name in the link."
    • removedOutput schema / properties / url / description
      Removed value: -"Public download link; anyone holding it can read the file until it expires."
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover readOnly/openWorld/idempotent/destructive, but the description adds substantial context: the link is public to anyone, TTL is capped at 24 hours, every call stores a new copy (explaining the non-idempotent hint concretely), content is detected from bytes with an explicit 415 list, and a 20 MB cap applies. Pricing (USD 0.005, no free tier) and expected latency are also disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Most content earns its place, but expiry is stated twice ('expires in 24 hours' and 'links expire within 24 hours'), the 'utilpeek:' prefix and latency figure are marginal, and pricing/docs/abuse contact are packed into one long run-on block that is not well front-loaded.

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?

Given an output schema exists, the description need not describe the return value, yet it covers everything else an agent needs: size limit, allowed/refused types, TTL bounds, public-link exposure, cost, and non-idempotency. Nothing material is missing for correct invocation.

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 coverage is 100%, so the schema already documents all three parameters including the 'extension is not trusted' caveat. The description adds little beyond 'default 24, the most' for ttl_hours, so baseline 3 is appropriate.

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 first sentence names a specific verb and resource ('Upload a file and get a download link') and states the scope (expires in 24 hours). No sibling in the catalog performs uploads, and the resource produced (a public link) is unambiguous.

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

Usage Guidelines3/5

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

Usage context is implied clearly (share a file by link) and the content-type/415 exclusions tell the agent when the call will fail. However, no alternative tool or condition for choosing a different approach is named, and the 'over HTTP the file may also be the raw request body' note is a transport detail rather than routing guidance.

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.