Wise MCP Server

List addresses

list_addresses

Read-onlyIdempotent

Retrieves addresses saved on Wise account profiles, enabling AI agents to inspect stored address details for recipients or profiles before payment setup.

Instructions

The addresses saved on the Wise account's profiles.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

C2.7/5.0

Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is well covered. The description adds only that addresses are saved on account profiles; it does not explain pagination, whether all profiles or the active profile are covered, ordering, or any other behavior beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no wasted words, but it is a sentence fragment and does not front-load a clear action. The sentence is compact yet under-specified rather than structurally strong.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple zero-parameter read tool, the description is still too thin because there is no output schema and it does not say whether the result covers all profiles or the active profile, nor what fields an address contains. An agent can call it, but it cannot confidently predict the returned scope or content.

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 has zero parameters and complete schema coverage, so there are no parameter semantics to document. The baseline score of 4 applies because the description does not need to compensate for any schema gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase rather than a verb-and-resource statement, and it largely restates the name/title. It does add that the addresses belong to Wise account profiles, which gives some scope and helps distinguish it from profiles or recipients, but the action 'list' is only inferable from the tool name.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool instead of related siblings such as list_profiles, get_profile, list_recipients, or get_recipient. The agent must infer the intended use entirely from the tool name.

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