Skip to main content
Glama

Download asset

download_asset
Destructive

Get a generated (or uploaded) file. asset is an asset id or the asset url from a job status. Locally (stdio) the file is saved to path (default: current directory, named after the asset id) and the saved path is returned. Remotely (HTTP) nothing is saved: a short-lived signed download URL is returned instead, and path/overwrite are ignored (the result says so); download the url yourself.

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": {
      "asset": "<asset>"
    },
    "name": "download_asset"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo
assetYes
overwriteNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=true; the description explains the mechanism behind each, namely that a file is written to disk locally (with an overwrite flag) and that a short-lived external URL is returned over HTTP. It also flags that `path`/`overwrite` are silently ignored remotely and that the result states so, which prevents a common misuse. It stops short of stating permission or failure behavior.

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?

Front-loaded with the one-line purpose, then transport-specific behavior in a compact two-clause structure. Every sentence adds actionable information: default path, filename derivation, return value, and the remote no-op caveat.

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?

Complete for a 3-parameter tool with an output schema: parameters and both return shapes are covered, and the transport-dependent semantics are disclosed. Minor omission is the exact local-overwrite behavior, but the output schema relieves the description of explaining result structure.

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 0% schema description coverage, the description carries the full burden and largely succeeds: `asset` accepts an id or URL, `path` defaults to the current directory and derives the filename from the asset id, and `overwrite` is ignored in remote mode. What `overwrite` does locally (replace an existing file) is only implied rather than stated.

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 generated (or uploaded) file') and immediately clarifies that the `asset` argument accepts either an id or a job-status URL. An agent knows exactly what this does and can separate it from list_assets or upload_asset without opening a schema.

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?

Gives concrete usage context by explaining the two transports: locally it saves a file to `path`, remotely it returns a signed URL and ignores `path`/`overwrite`. That is effectively 'when this behaves how' guidance, though it does not explicitly name an alternative tool to use instead.

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