Skip to main content
Glama

Get Download URL

get_download_url
Read-onlyIdempotent

Get a presigned S3 URL to download a specific applied template file by its ID. Format is read from the stored file.

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": {
      "fileId": "<fileId>"
    },
    "name": "get_download_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileIdYesApplied template file ID

Output Schema

NameRequiredDescriptionDefault
kindYes
fileIdNo
formatNo
statusYes
viewUrlNo
fileNameNo
downloadUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a read-only, idempotent, non-destructive, non-open-world operation, so the safety profile is covered. The description does add real behavior: it returns a presigned S3 URL and derives the file format from stored metadata rather than a caller parameter. It omits the practically important detail of URL expiry/validity window, which is the main behavioral risk for a presigned link.

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?

Two sentences, zero padding, with the core action and return artifact front-loaded. The second sentence adds a non-obvious constraint (format is not caller-selectable) in minimal space.

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?

With a rich annotation set and an output schema that can carry the URL and metadata, the description is nearly sufficient for an agent to call it correctly. The remaining gap is the absence of any statement about link lifetime or what the output schema's fields represent operationally.

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% with a single well-described required UUID parameter, so the baseline applies. The description reinforces that the ID refers to an applied template file, matching the schema wording, but adds no format, source, or validation detail beyond it.

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?

States a specific verb and resource ('Get a presigned S3 URL') plus the scope ('to download a specific applied template file by its ID'), which is clear enough for an agent to act on. It does not distinguish itself from the similarly named sibling get_user_file_url, so the agent must infer the difference between applied-template files and user files.

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 is only implied: the tool is the way to obtain a download link for an applied template file, and 'by its ID' hints the fileId comes from an applied template. There is no explicit when-to-use / when-not-to-use statement and no named alternative such as get_user_file_url, so routing between the two URL tools is left to inference.

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