Skip to main content
Glama

List profiles

wise_list_profiles
Read-only

List the Wise profiles a personal API token can access, including personal and business accounts, to retrieve the profile IDs required by other Wise tools.

Instructions

List the Wise profiles (personal and business) this token can access. Most other tools need a profile ID from here.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/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 still contributes beyond them by disclosing the access-scoping behavior (only profiles this token can reach) and the fact both personal and business profile types appear in the result, which shapes how an agent interprets an empty or partial response.

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, zero preamble, with the identity of the tool front-loaded and the workflow hint placed immediately after. Every clause carries information an agent can act on.

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?

There is no output schema, so the description must convey roughly what comes back, which it does by naming profile type and token scoping. It stops just short of describing the individual fields (such as the profile ID itself) that downstream tools require, a small but real gap for the designated entry-point tool.

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 schema declares an empty object with zero parameters, so there is nothing for the description to explain and the baseline applies. No parameter-level compensation is needed or attempted.

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?

"List the Wise profiles (personal and business) this token can access" gives a specific verb (list), resource (Wise profiles), the shape of the result (personal and business), and the scope (token-visible only). That scope detail is what separates this from a naive full-catalog listing and is enough for an agent to pick it out of the sibling set.

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?

The second sentence tells the agent when this tool matters: it is the prerequisite source of a profile ID that "most other tools" consume, which is real ordering guidance rather than a restatement. It stops short of naming which sibling to call next or stating what to do if zero profiles are returned, so it is clear context without explicit alternatives.

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