Skip to main content
Glama
Sign In
Agentic AQUA

Agentic AQUA

Official
by AquaWallet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

unified_balance

Retrieve Bitcoin and Liquid network balances from a unified wallet to view combined holdings in one place.

Instructions

Get balance for both Bitcoin and Liquid networks (unified wallet)

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

Input Schema

NameRequiredDescriptionDefault
wallet_nameNoName of the walletdefault

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It states the tool gets a balance, which is a safe read operation. However, it does not disclose any potential side effects, rate limits, or requirements beyond that.

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?

Single sentence, no wasted words, directly states the tool's function. Front-loaded with the key action and resource.

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 balance getter with no output schema, the description is adequate but does not hint at return format (e.g., combined balance or separate values). Slightly incomplete given the lack of output schema.

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 has one parameter with description 'Name of the wallet'. Description does not add any new meaning beyond the schema. Since schema coverage is 100%, baseline 3 is appropriate.

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?

Description clearly states verb 'Get' and resource 'balance for both Bitcoin and Liquid networks (unified wallet)'. It distinguishes from siblings btc_balance and lw_balance by emphasizing the unified view.

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?

No explicit when-to-use or when-not-to-use guidance. The existence of sibling tools btc_balance and lw_balance implies this is for a combined view, but alternatives are not named or contrasted.

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