Skip to main content
Glama

Shielded balance

get_balance

Check the agent's shielded USDG balance on Nuluvium, see per-note funds and the deposit wallet for new deposits, and identify the largest note available to route an order.

Instructions

Shows the agent's shielded USDG balance on Nuluvium, per note, and the deposit wallet that funds new deposits. One order is paid from one note, so the largest note is the largest order you can route right now.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description must carry the behavioral load, and 'Shows' correctly implies a side-effect-free read. More importantly it discloses the non-obvious domain rule that one order is paid from one note, which changes how an agent interprets the result. Gaps remain: no statement of units/decimals, refresh behavior, or what an empty wallet returns.

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 with no filler. The return composition (per-note balance, deposit wallet) is front-loaded, and the interpretive rule about notes follows immediately after as supporting context.

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?

For a zero-param read tool with no output schema, the description usefully sketches what comes back (per-note amounts plus a deposit wallet) and how to reason about them. It's a bit thin on the account relationship between shielded balance and deposit wallet, which is the one thing an agent might misread when deciding whether a deposit is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so schema coverage is moot and the baseline of 4 applies. The description correctly introduces no parameter vocabulary, so nothing is left dangling.

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?

Names a specific verb and resource: shows the shielded USDG balance on Nuluvium, broken down per note, plus the deposit wallet. The final sentence explains note semantics, which makes the resource's shape unambiguous and clearly sets it apart from order/fill readers like get_orders and get_fills.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a concrete decision rule tied to a sibling's domain: the largest note caps the largest routable order, implying this should be read before route_order. It stops short of naming route_order or stating exclusions (e.g., use get_orders for order history), so it's clear context but not a full when/when-not map.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.