Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update payment route

update_virtual_account
DestructiveIdempotent

Change a virtual account's deposit handling mode to auto-payout, hold, or manual, so you can control how incoming deposits are processed.

Instructions

Update virtual account settings (e.g., deposit handling mode)

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

Input Schema

NameRequiredDescriptionDefault
customerIdYesThe customer ID
virtualAccountIdYesThe virtual account ID to update
depositHandlingModeYesNew deposit handling mode

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already disclose that this is a destructive, idempotent, non-read-only mutation. The description adds only that it updates virtual account settings such as deposit handling mode; it does not explain side effects, reversibility, or what happens to existing settings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and waste-free. It is terse, but the brevity is not due to unnecessary wording; the missing detail belongs to other dimensions rather than conciseness.

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?

The schema and annotations cover parameters and the destructive/idempotent safety profile, but for a destructive update the description is still thin. It does not explain the practical effect of each deposit handling mode or any prerequisites for changing the account.

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 all three parameters are already documented in the schema. The description mentions deposit handling mode as an example but does not add meaning beyond the enum values or explain the roles of customerId and virtualAccountId.

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?

It clearly states the verb and resource: update virtual account settings, with deposit handling mode as an example. It is distinguishable from create/list virtual account siblings, though it does not explicitly compare against related route-update tools.

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

Usage Guidelines2/5

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

The description gives no explicit guidance on when to use this tool versus alternatives such as update_route_destination, create_virtual_account, or get_virtual_account_history. Usage is only implied by the verb 'update'.

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