Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List transfers

list_transfers
Read-onlyIdempotent

Retrieve and filter stablecoin transfers by status, type, or customer to review payment activity and track transfer progress.

Instructions

List transfers with optional filters for status, type, or customer

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_transfers"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by transfer type
statusNoFilter by transfer status
pageSizeNoNumber of transfers per page (default: 20)
pageTokenNoToken for the next page of results
customerIdNoFilter by customer ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed2 schema fields changedv2.4.0
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "CREATED",
-  "COMPLIANCE_HOLD",
-  "AWAITING_FUNDS_COLLECTION",
-  "FUNDS_COLLECTED",
-  "PAYMENT_SUBMITTED",
-  "PAYMENT_PROCESSED",
-  "COMPLETED",
-  "FAILED",
-  "CANCELLED",
-  "EXPIRED"
-]New value: +[
+  "created",
+  "compliance_hold",
+  "awaiting_funds_collection",
+  "funds_collected",
+  "in_progress",
+  "payment_submitted",
+  "payment_processed",
+  "completed",
+  "failed",
+  "cancelled",
+  "expired"
+]
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "TRANSFER_TYPE_ONRAMP",
-  "TRANSFER_TYPE_OFFRAMP"
-]New value: +[
+  "onramp",
+  "offramp"
+]
  3. First observedv1.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds nothing about ordering, pagination behavior, or whether results include all transfers unfiltered when no params are supplied — modest additional value on top of the annotations.

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 with no filler; the resource leads and the optional filters follow. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and for a paginated list tool the description never explains how pageToken/pageSize interact or what the response envelope looks like. With five all-optional params and no annotations gap, this is adequate but leaves a real question unanswered.

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%, with enum values and descriptions for status, type, customerId, pageSize and pageToken. The description only restates three filter names and omits any mention of the pagination parameters, so it adds no meaning beyond the schema. Baseline 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?

Names a specific verb and resource ('List transfers') and enumerates the filter dimensions available. However, it does not distinguish this from the related single-record sibling get_transfer or from list-style siblings such as list_balance_activity, leaving disambiguation to the name alone.

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?

The phrase 'with optional filters' implies the intended use (browse/filter transactions) but never states when to prefer this over get_transfer for a known ID, nor when to page through results. Usage is implied rather than prescribed.

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