Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get payment route history

get_virtual_account_history
Read-onlyIdempotent

Retrieve the transaction history for a virtual account, including deposits and payouts, to review account activity by customer ID and virtual account ID.

Instructions

Get the activity history for a virtual account (deposits, payouts, etc.)

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of events to return (default: 10)
customerIdYesThe customer ID
virtualAccountIdYesThe virtual account ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.6.11
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv2.4.0
    • removedInput schema / properties / eventType
      Removed value: -{
-  "description": "Filter by event type",
-  "enum": [
-    "funds_scheduled",
-    "funds_received",
-    "payment_submitted",
-    "payment_processed",
-    "in_review",
-    "refund",
-    "microdeposit",
-    "account_update",
-    "deactivation",
-    "activation"
-  ],
-  "type": "string"
-}
  3. First observedv1.4.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this as a read-only, idempotent, non-destructive operation, so the safety bar is lower. The description adds that the result covers activity types like deposits and payouts, but does not mention ordering, pagination beyond limit, or freshness.

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?

It is a single sentence with zero waste, front-loading the verb and resource. The parenthetical examples are the only extra detail and they directly clarify the activity scope.

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?

For a simple read tool with complete schema coverage and annotations, the description is barely sufficient. It does not explain return shape, ordering, or pagination behavior, and there is no output schema to fill that gap.

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 input schema, including the default for limit. The description adds no parameter-level detail beyond the schema, which is the expected baseline when coverage is high.

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?

The description states a specific verb and resource: get the activity history for a virtual account, with examples of deposits and payouts. It is clear what the tool does, though it does not explicitly distinguish itself from nearby tools like list_balance_activity or the virtual-account CRUD siblings.

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?

It gives no explicit guidance on when to use this tool versus alternatives such as list_balance_activity or list_virtual_accounts. The usage is only implied by the purpose statement, with no exclusions or prerequisites mentioned.

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