Skip to main content
Glama

Typebar (formerly SuperDocs)

request_download_url

Returns a short-lived (15-minute) GET URL plus a ready-to-run curl_example. An agent with shell access can run the curl_example directly to save the exported file to the working directory, so the bytes never pass through its context window; clients without shell execution (or callers who only want the link) can use the signed URL directly. Generates the document in the requested format and returns a time-limited signed download URL. Specify format as 'pdf', 'docx', 'html', 'markdown', or 'txt' (legacy 'doc' also accepted).

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": {
      "session_id": "<session_id>"
    },
    "name": "request_download_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoExport format (docx, pdf, html, markdown, txt).docx
optionsNoCustomization (paper, margins, filename, watermark, etc.). Mirrors ExportRequest.options.
filenameNoOptional Content-Disposition filename for the download (without extension). Auto-detected from the document's first heading if not provided.
session_idYesSession ID whose current document should be exported and packaged for download.

Output Schema

NameRequiredDescriptionDefault
formatYes
filenameYes
expires_atYes
curl_exampleYes
download_urlYes
expires_in_secondsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The description is highly transparent, disclosing the short lifespan of the URL (15 minutes) and, critically, explaining the technical mechanism of the download—that bytes 'never pass through its context window' when using the shell example. This is powerful behavioral context beyond the schema.

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?

While dense, the description is highly efficient. It front-loads the outcome (URL/curl) and moves logically through use-case implications and input constraints, ensuring every sentence carries high operational weight.

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 the complexity of the input schema (10+ parameters in nested objects), the description provides the necessary high-level context regarding time limits, download mechanisms, and the purpose of the fields, making it extremely complete for an agent to utilize this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the description's primary value is in framing the entire export process. It explicitly groups and defines the customization options (format, paper size, margins) rather than just listing parameters, providing essential semantic context for the complex `options` object.

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 purpose is stated clearly: 'Returns a short-lived (15-minute) GET URL' and 'Generates the document'. It distinguishes itself as a download utility, which is critical given the context of document management siblings.

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?

It provides explicit usage guidelines by defining two distinct workflows: using a direct signed URL (for clients without shell access) versus running a `curl_example` (for agents with shell access). This prevents agent confusion and defines operational boundaries.

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.