Skip to main content
Glama

Get a download link

knacco_get_download_link
Read-only

Create a signed download URL for one owned file using files[].assetId from knacco_get_product_guide. Returns url, expiresInSec (30), fileName, mimeType and sizeBytes. Retrieve the file promptly; request a new link after expiry. Requires content:read and file entitlement; does not purchase products or return file bytes. Limited to 60 link requests per account per 10 minutes. Treat the signed URL as private.

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": {
      "assetId": "<assetId>"
    },
    "name": "knacco_get_download_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYesExact files[].assetId from knacco_get_product_guide. Identifies one downloadable file, not a product slug or URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: 30-second expiry, a rate limit of 60 link requests per account per 10 minutes, required content:read scope plus file entitlement, and a privacy warning to treat the signed URL as secret. The readOnlyHint is consistent — it mints a URL without mutating stored data.

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-loads the action, then the value source, then the return fields, then operational constraints and limits. Every clause carries a distinct, actionable fact with no padding.

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?

With no output schema, the description enumerates the return payload (url, expiresInSec, fileName, mimeType, sizeBytes) and covers auth, rate limits, and expiry — everything needed to call it correctly and handle the result.

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% and the schema already states that assetId is the exact files[].assetId, not a slug or URL. The description repeats that guidance by naming the sibling tool that produces the value, which is mildly useful but adds no new syntax or format detail, so baseline 3 applies.

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 ("Create a signed download URL for one owned file") and pins the exact scope: one file identified by files[].assetId from knacco_get_product_guide. An agent can distinguish this from library/search siblings 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?

Establishes the prerequisite chain (get the assetId from knacco_get_product_guide first) and warns to retrieve the file promptly and re-request after expiry, plus explicit negatives: does not purchase products or return file bytes. It stops short of naming an alternative for multi-file or bulk retrieval, so 4 rather than 5.

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