Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Change payment route destination

update_route_destination
DestructiveIdempotent

Change the payout wallet on an existing payment route to support wallet rotation. This feature updates the destination address for future deposits without requiring a new virtual account.

Instructions

Change the payout wallet on an existing payment route. Deposits after this point are paid out to the new address; use it when a customer rotates wallets rather than creating a second route.

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": {
      "customerId": "<customerId>",
      "virtualAccountId": "<virtualAccountId>",
      "destinationAddress": "<destinationAddress>",
      "destinationPaymentRail": "<destinationPaymentRail>"
    },
    "name": "update_route_destination"
  }
}

Input Schema

NameRequiredDescriptionDefault
customerIdYesThe customer ID
virtualAccountIdYesThe payment route (virtual account) ID
destinationAddressYesNew payout wallet address
destinationCurrencyNoStablecoin to receiveusdt
destinationPaymentRailYesBlockchain network the new address belongs to

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/5.0
Behavior4/5

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

Beyond the structural hints provided by annotations (destructive/writable), the description provides crucial operational behavioral context. Specifically, it notes that 'Deposits after this point are paid out to the new address,' defining the functional and temporal impact of the change.

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 highly efficient, front-loading the primary function in the first sentence and following up with the critical usage context in the second.

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?

Given that this is a mutation tool requiring specific business context (rotation vs. creation), the description is complete. It tells the agent exactly what the tool is and under what conditions it should be invoked.

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?

Since schema coverage is 100%, the schema itself provides the necessary semantics for the parameters. The description doesn't add semantic meaning to the data fields themselves beyond defining the overall action on those resources. Baseline 3 is appropriate.

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 clearly identifies the action ('Change the payout wallet') and the target resource ('existing payment route'). It also differentiates itself from sibling tools by specifying the use case: rotating wallets instead of creating a new route.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit instructions on when to use the tool: 'use it when a customer rotates wallets rather than creating a second route.' This is a definitive guide against creating a new route.

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