Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List documents

list_documents
Read-onlyIdempotent

Fetch documents attached to a transfer or payment route deposit, newest first. Specify the transaction ID and whether it's a transfer or deposit.

Instructions

List the documents attached to a transfer or a payment route deposit, newest first.

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

Input Schema

NameRequiredDescriptionDefault
onYesWhat the document belongs to: a transfer, or a deposit on a payment route
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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is fully covered. The description adds one useful behavioral fact beyond that: results are returned newest first. It does not describe pagination or what a returned entry contains.

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?

A single, front-loaded sentence that states the action, the scopes, and the ordering with zero filler. Nothing extraneous and nothing important buried.

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 two-parameter read tool with full schema coverage and comprehensive annotations, the description covers what it needs. The only gap is that with no output schema, it doesn't describe the shape of a returned document, but that is a minor omission.

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%, and both parameters are fully documented there, including the enum meaning of 'on' and where 'transactionId' comes from. The description adds no additional parameter detail, so the baseline of 3 applies.

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 clear verb+resource (list documents) plus the two scopes it covers (transfer or payment route deposit) and the ordering (newest first). An agent can distinguish it from add_document, get_document_download_url, and delete_document, though siblings are not named explicitly.

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 only implied by the scoping: the tool is for enumerating documents attached to a known transfer or deposit. No explicit when-to-use/when-not or alternatives (e.g., download vs list) are stated; the deposit-ID source hint lives in the schema rather than the description.

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