Skip to main content
Glama
Sign In
Stables MCP Server

Stables MCP Server

Official
by stables-money
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get balance wallet

get_balance_wallet
Read-onlyIdempotent

Retrieve the deposit wallet address and status for topping up your balance on a chosen network; the address is available only when active.

Instructions

Get the deposit wallet that tops up your balance on one network, and its status. The address is only present once the status is 'active'.

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": "get_balance_wallet"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkNoNetwork (default polygon)

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.8/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description still adds a genuinely useful fact beyond them: the address field is only populated when status is 'active'. That conditionality is exactly what an agent needs to interpret an empty address correctly rather than reporting a broken wallet.

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?

Two short sentences, zero filler, with the resource definition first and the address-availability caveat attached where it matters.

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 carries the return-value burden and does so reasonably: it names the two things returned (wallet address, status) and flags the conditional. It stops short of saying what other wallet metadata comes back or what a status other than 'active' implies.

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 coverage is 100% with the enum and default (polygon) documented, so baseline 3 applies. The description reinforces scope with 'on one network' but adds no syntax or behavior beyond what the schema already states.

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: retrieves the deposit wallet for one network plus its status, and characterizes the wallet as the one that 'tops up your balance'. This distinguishes it from the adjacent get_balance (balances, not wallets) and create_balance_wallet (provisioning), though neither sibling is named explicitly.

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?

Usage is implied: fetch a network's deposit wallet and status. There is no explicit when-to-use/when-not guidance and no pointer to create_balance_wallet if no wallet exists yet, which is the most likely failure path given a sibling with that exact name.

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