Skip to main content
Glama

Link to open or download one of my documents

document_download_link
Read-onlyIdempotent

A site URL to open or download one of your own documents. File documents return a gated download URL that only works in a browser signed in as you (access is checked again when it is opened; no file bytes pass through this connection). Page documents (certificates, invoices, quotations) return their page URL.

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>"
    },
    "name": "document_download_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesDocument ref (from documents_list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that file documents return a gated URL that only works in a browser signed in as the caller, that access is re-checked on open, and that no file bytes pass through this connection. That is exactly the kind of auth and data-flow context an agent needs before deciding to surface a 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 tight sentences, front-loaded with the core outcome (a URL) and then the file-vs-page branching. No filler or restated title.

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 correctly explains what is returned for each document class and the security caveat on the download URL. Nothing an agent needs to call it or interpret the result is missing.

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 ref parameter already documents its pattern and that it comes from documents_list, so the schema carries the load. The description adds no further meaning about the ref format or prefix semantics, which is the expected baseline.

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: returns a site URL to open or download one of your own documents, and splits the behavior into file documents vs page documents (certificates, invoices, quotations). That is concrete and distinguishable from a plain document_get, though it never names a sibling to contrast with.

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 implied by 'one of your own documents' and the file/page distinction, but there is no explicit when-to-use-this-vs-alternatives guidance (e.g., when to call this instead of document_get or documents_list). The ref source is only mentioned in the schema, not the description.

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