Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update payment route allowed sender

update_route_whitelist_account
DestructiveIdempotent

Update or disable a whitelisted source account on an AUD payment route by submitting the full BSB, account number, and enabled status record.

Instructions

Change or disable a whitelisted source account on an AUD payment route. Send the full record: BSB, account number and status.

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>",
      "sourceAccountId": "<sourceAccountId>",
      "bsbNumber": "<bsbNumber>",
      "accountNumber": "<accountNumber>",
      "enabled": "<enabled>"
    },
    "name": "update_route_whitelist_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYesfalse to stop accepting deposits from it
bsbNumberYesSource account BSB
customerIdYesThe customer ID
accountNumberYesSource account number
sourceAccountIdYesThe whitelist entry ID (from list_route_whitelist)
virtualAccountIdYesThe AUD payment route (virtual account) ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / sourceAccountId / maximum
      Added value: +9007199254740991
  2. Addedv2.4.0

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already disclose destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds useful scope by saying this applies to an AUD payment route and can disable a source account, but it does not elaborate on the destructive consequence beyond the word 'disable'.

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 two short sentences, front-loaded with the operation and followed by the key input requirement. Every sentence is relevant and there is no filler.

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?

Given the destructive and idempotent annotations plus the fully described six-parameter schema, the description is minimally adequate. It does not explain how to obtain sourceAccountId or warn about the effect of disabling beyond the schema's own field description.

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 documents all six required parameters. The description says to send the full record but only enumerates BSB, account number, and status, omitting customerId, virtualAccountId, and sourceAccountId; the baseline score of 3 is appropriate because the schema carries the detailed semantics.

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: change or disable a whitelisted source account on an AUD payment route. It clearly distinguishes an update operation from sibling tools like add_route_whitelist_account and list_route_whitelist.

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 'change or disable a whitelisted source account' implies this is for updating an existing whitelist entry, not creating one. However, it does not explicitly name alternatives or state when to use add_route_whitelist_account versus this tool.

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