Skip to main content
Glama

Get a download link for one of my files

my_app_download_link
Read-onlyIdempotent

A one-time, 2-minute download link for one file of your own app or subscription (needs ref from my_apps_list and asset_ref from my_app_get). The link only works when opened in a browser where you are signed in to Barmaan as the same account; it cannot be used once, after it expires, or if the subscription is no longer active. Returns the site path (not a public URL), file name, size and SHA-256.

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": {
      "ref": "<ref>",
      "asset_ref": "<asset_ref>"
    },
    "name": "my_app_download_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesItem reference from my_apps_list, e.g. ENT-ABCD2345.
asset_refYesFile reference from my_app_get, e.g. AST-ABCD2345.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say read-only, non-destructive, non-open-world and idempotent; the description adds the substantive behavior: 2-minute TTL, single use, browser/session-bound authentication requirement, subscription-active precondition, and the fact that the returned value is a site path rather than a public URL. These are exactly the failure modes an agent needs before calling. The 'one-time' link wording is consistent with a read-only, non-destructive tool.

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?

Three dense sentences, front-loaded with what the tool produces before the constraints and return shape; almost nothing is wasted. Minor deduction for the slightly muddled phrase 'it cannot be used once, after it expires', where 'used once' reads ambiguously against the earlier 'one-time' framing.

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?

No output schema exists, yet the description enumerates the return payload (site path, file name, size, SHA-256) and clarifies the path is not a public URL. Combined with prerequisites, expiry, and auth conditions, an agent has everything needed to call this correctly for a two-parameter read tool.

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?

Schema coverage is 100% and the schema already documents both parameters with patterns and examples. The description adds provenance meaning beyond the schema — which sibling tool produces each reference — which helps an agent sequence calls correctly, though it adds no format or validation detail.

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 — a one-time, 2-minute download link for exactly one file belonging to the caller's own app or subscription. Scope qualifiers ('one file', 'your own', 'of your app or subscription') let an agent distinguish it from the sibling document_download_link without opening either 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?

Explicitly names the prerequisite tools and which parameter comes from which: ref from my_apps_list and asset_ref from my_app_get. It also states the operational conditions under which the link fails. It stops short of naming an alternative tool or an explicit when-not-to-use case, so it is clear context rather than full 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.

Resources