Wise MCP Server

List profiles

list_profiles

Read-onlyIdempotent

Retrieves all Wise personal and business profiles available to the token, including their IDs. Use it first when multiple profiles may exist, then pass the chosen profile ID as profile.

Instructions

List the Wise profiles this token can act for, personal and business, with their ids. Call this first when more than one profile may exist, then pass the id as profile.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, and the description still adds value: results are scoped by token permissions and span both personal and business profile types. It doesn't discuss ordering, empty results, or volume, which are minor for a small enumeration call.

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 sentences, no filler, with the what (list profiles and ids) stated before the when (call first) and the downstream handoff. Every clause carries information.

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

Completeness5/5

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

For a zero-parameter, read-only listing tool with no output schema, the description fully covers what is returned (profiles of both types with ids) and why an agent should call it. Nothing needed to invoke it correctly is missing.

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?

There are zero input parameters, so the baseline is 4. The description goes slightly further by explaining that the returned id is the value other tools expect in their `profile` field, giving the output meaning even without a declared output schema.

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 names a specific verb and resource ('List the Wise profiles') and scopes it precisely: profiles 'this token can act for, personal and business, with their ids'. That clearly separates it from the singular sibling get_profile and from unrelated list_* tools.

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?

It gives an explicit trigger ('Call this first when more than one profile may exist') and the follow-up action ('pass the id as `profile`'). It stops short of naming get_profile as the single-profile alternative, so the routing guidance is strong but not fully exhaustive.

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