Skip to main content
Glama

Get balances

wise_get_balances
Read-only

Retrieve multi-currency Wise balances for a profile, including each currency's amount, reserved amount, and balance ID for balance checks and reconciliation.

Instructions

Get multi-currency balances for a profile: amount, reserved amount and balance ID per currency.

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

Input Schema

NameRequiredDescriptionDefault
typesNoComma-separated: STANDARD, SAVINGSSTANDARD
profileIdNoWise profile ID. Optional when WISE_PROFILE_ID is set; get it from wise_list_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.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, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful context about what the call returns (per-currency amounts, reserved amounts, balance IDs), but says nothing about authorization scope, profile-type applicability, or behavior when a profile has no balances.

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 no filler; the resource comes first and the returned fields follow. Nothing in it is redundant with the schema or removable.

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 only two optional, fully documented parameters and no output schema, the description is nearly self-sufficient and does explain the shape of the returned data. The remaining gap is the absence of any indication of when this tool should be preferred over related balance/statement tools.

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%, and the schema already documents both parameters in detail, including the WISE_PROFILE_ID fallback and the STANDARD/SAVINGS values for types. The description adds no parameter meaning beyond the schema, so the baseline of 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?

States a specific verb and resource ("Get multi-currency balances for a profile") and enumerates the returned fields (amount, reserved amount, balance ID per currency). It is clear what the tool does, though it never contrasts itself with the close sibling wise_get_balance_statement, so an agent must infer which one to pick.

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?

Provides no explicit when-to-use or when-not-to-use guidance, and does not name any alternative such as wise_get_balance_statement. Usage is only implied by the purpose statement; an agent can guess this is the listing tool but gets no routing help.

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