Skip to main content
Glama
stables-money

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_virtual_accounts

Fetch payment routes (virtual accounts) for a specific customer or all customers. Filter by status, limit results, and paginate through routes.

Instructions

List payment routes (virtual accounts) for one customer, or across every customer when customerId is omitted

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of accounts to return
statusNoFilter by account status
customerIdNoOnly this customer's routes; omit to list routes across all customers
startingAfterNoReturn routes after this route ID (the last ID of the previous page)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.4.0
    • changedInput schema / properties / customerId / description
      Previous value: -"The customer ID to list virtual accounts for"New value: +"Only this customer's routes; omit to list routes across all customers"
    • addedInput schema / properties / startingAfter
      Added value: +{
+  "description": "Return routes after this route ID (the last ID of the previous page)",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "customerId"
-]
  2. First observedv1.4.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses one behavioral trait, the default cross-customer scope when customerId is omitted, but says nothing about read-only nature, result volume, pagination behavior, or authorization requirements. For a mutation-free listing tool this is thin but not misleading.

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, well-formed sentence with no filler. The scope-defining condition is placed at the end where it reads naturally, and nothing is repeated.

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?

With no annotations and no output schema, the description is the only place for behavioral context, and it covers just the scope default. Pagination expectations (how limit and startingAfter interact), return shape, and whether an unbounded all-customer listing is safe to call are left unaddressed. Adequate but with clear gaps for a 4-parameter listing tool.

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 four parameters (limit, status, customerId, startingAfter) are already documented in the schema. The description's customerId clause restates what the schema property already says, adding no new syntax, format, or constraint detail. Baseline 3 applies when the schema does the heavy lifting.

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 specific verb (List) and resource (payment routes / virtual accounts), including the useful synonym mapping that ties 'payment routes' to 'virtual accounts'. The scope distinction (one customer vs. all customers) is stated. It stops short of naming a sibling like get_virtual_account_history to disambiguate further, but the purpose itself is unambiguous.

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 description implies usage by describing the two modes: pass customerId for one customer, omit it to list across all. There is no explicit when-not guidance or pointer to alternatives such as get_virtual_account_history for a single account's events. Usage is inferable but not routed.

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