Skip to main content
Glama
Sign In
Wise MCP Server

Wise MCP Server

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wise_list_balances

Read-only

Retrieves balance accounts for a Wise profile, including standard multi-currency accounts and savings jars.

Instructions

List balance accounts for a profile. STANDARD = one per currency (the multi-currency account). SAVINGS = jars (user-named buckets). Default returns only STANDARD.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "profileId": "<profileId>"
    },
    "name": "wise_list_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
typesNoComma-separated balance types. Known values: STANDARD (one per currency), SAVINGS (jars, multiple per currency). Default STANDARD.STANDARD
profileIdYesProfile ID (from list_profiles)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A4/5.0
Behavior4/5

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

Annotations indicate readOnlyHint and openWorldHint. The description adds behavioral context (default returns only STANDARD, SAVINGS jars explanation) beyond annotations, with no contradiction.

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 concise sentences front-loading purpose, followed by relevant type details with no unnecessary words.

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 2 parameters fully described in schema and no output schema, the description covers key behavior (default type) but omits potential details like pagination or response format. Adequate for a simple list tool.

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 covers 100% of parameters with descriptions. The description repeats schema info (STANDARD vs SAVINGS) without adding significant new meaning, so 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?

The description clearly states 'List balance accounts for a profile' with specific details on types (STANDARD vs SAVINGS), effectively distinguishing it from sibling tools like wise_get_balance.

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?

While it explains default behavior (STANDARD) and type definitions, it lacks explicit guidance on when to use this tool versus alternatives like wise_get_balance for retrieving a single balance.

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