Wise MCP Server

Account activity

list_activities

Read-onlyIdempotent

Retrieve a Wise profile's activity feed of transfers, card spending, conversions and deposits, newest first, with type, status and date filters plus cursor pagination.

Instructions

The profile's activity feed, newest first, as the Wise app shows it: transfers, card spending, conversions and money in, each with a title, amounts and status. Pages with cursor.

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

Input Schema

Name	Required	Description
`size`	No	How many per page, 1-100. Defaults to 20.
`type`	No	Only one kind, such as TRANSFER, CARD_PAYMENT, CONVERSION or BALANCE_DEPOSIT.
`since`	No	Only activity on or after this time, ISO 8601, such as 2026-11-01T00:00:00Z.
`until`	No	Only activity before this time, ISO 8601.
`cursor`	No	The `next` value from the previous page.
`status`	No	Only one status, such as COMPLETED, PENDING or CANCELLED.
`profile`	No	The Wise profile id to act for. Defaults to WISE_PROFILE_ID, else the only business profile. See list_profiles.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description adds ordering ('newest first'), the paging mechanism via cursor, and the shape of each item (title, amounts, status) — context the annotations do not contain. It does not mention rate limits or what happens on an exhausted cursor, keeping it short of a 5.

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

Conciseness4/5

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

Two dense sentences with the resource and ordering front-loaded and paging appended last. The clipped phrasing ('money in', 'Pages with `cursor`') is efficient rather than confusing, though slightly telegraphic.

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 no output schema, the description usefully sketches the returned record (title, amounts, status) and the pagination contract, and the schema handles all parameters. What remains thin is the absence of guidance on choosing this over list_transfers.

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%, so all seven parameters are already documented including defaults, bounds and ISO 8601 examples. The description only echoes the cursor paging behavior, adding no new parameter meaning; baseline 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+resource: returns the profile's activity feed including transfers, card spending, conversions and money in. That distinguishes it clearly from list_transfers, which returns only one of those kinds, though the description never names that sibling explicitly.

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?

Usage is only implied — that this is the combined feed means an agent could infer it should prefer list_transfers for transfer-only queries, but no when-to-use or when-not-to-use guidance is stated, and no prerequisites such as profile resolution are discussed.

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