Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List balance activity

list_balance_activity
Read-onlyIdempotent

List all balance credits received, showing the amount, network, transaction hash, and sender. Review your newest deposits first for full activity transparency.

Instructions

List deposits that have credited your balance, newest first, with amount, network, transaction hash and sender.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_balance_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoOnly this network
pageSizeNoResults per page (default 20)
pageTokenNonext_page_token from the previous page

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine context (result ordering, that only credited/settled deposits appear, the field set), but says nothing about pagination behavior, limits, or whether results span all networks by default when the filter is omitted.

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 front-loaded sentence with the ordering constraint and field list; every clause earns its place and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description usefully enumerates the returned fields (amount, network, transaction hash, sender), which is exactly the compensating detail needed. It falls short of complete only on pagination/filter behavior, which the schema partially covers.

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%, including an enum for network and bounds/defaults for pageSize and pageToken, so the schema carries the parameter burden. The description adds nothing about the network filter or paging, so the baseline 3 applies.

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?

Specific verb + resource with scope qualifiers: 'List deposits that have credited your balance', plus the ordering ('newest first') and the returned fields. 'Credited' implicitly separates it from list_pending_balance_deposits, but no sibling is named, so the differentiation is inferential rather than explicit.

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 'that have credited your balance' implies this shows settled, applied deposits rather than pending ones, which nudges toward the right tool. However, it never states when to use this versus get_balance, list_pending_balance_deposits, or get_virtual_account_history, and gives no exclusions or prerequisites.

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