Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get document download link

get_document_download_url
Read-onlyIdempotent

Creates a short-lived URL to download a document attached to a transfer or a payment route deposit using transaction and document IDs.

Instructions

Get a short-lived link to download a document attached to a transfer or a payment route deposit.

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": {
      "on": "<on>",
      "transactionId": "<transactionId>",
      "documentId": "<documentId>"
    },
    "name": "get_document_download_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYesWhat the document belongs to: a transfer, or a deposit on a payment route
documentIdYesThe document ID from list_documents
transactionIdYesThe transfer ID, or the deposit ID from get_virtual_account_history

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv2.4.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare this as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context that the link is short-lived, which is important for an agent deciding whether to use or cache it. It does not specify expiry duration or permission requirements, but the annotations carry much of the safety burden.

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?

The description is a single, front-loaded sentence with no filler. Every word contributes to identifying the operation and its key characteristic: short-lived link.

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?

For a simple 3-parameter read operation with full schema coverage and annotations, the description is largely complete. It explains what the tool returns (a short-lived link) and the resource scope. A minor gap is that it does not state link lifetime or whether the link is reusable, but this is not critical for correct invocation.

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 description coverage is 100%, so the schema already fully documents the three parameters, including enum values and ID provenance. The description adds only the general resource context ('transfer or payment route deposit'), which is already reflected in the schema's 'on' parameter.

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?

The description states a specific verb and resource: get a short-lived download link for a document attached to a transfer or deposit. It clearly distinguishes this from sibling document tools like list_documents or add_document.

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 the resource types mentioned, but the description does not explicitly say when to use this instead of list_documents or when a download link is preferable. The schema does route the agent to list_documents and get_virtual_account_history for IDs, but the description itself offers no explicit alternatives or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools