Skip to main content
Glama

List activities

wise_list_activities
Read-only

List recent Wise account activity such as card spend, transfers, conversions, and top-ups, with pagination via cursor and filters for date range and status.

Instructions

List recent account activity (card spend, transfers, conversions, top-ups). Paginate with nextCursor from the previous response's 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": "wise_list_activities"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
sinceNoISO 8601 timestamp
untilNoISO 8601 timestamp
statusNo
profileIdNoWise profile ID. Optional when WISE_PROFILE_ID is set; get it from wise_list_profiles.
nextCursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/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 and the bar is lower. The description adds useful context: the categories of activity surfaced and the cursor-chaining mechanism for pagination. It does not disclose default page size, sort order ("recent" is only implied), or result limits, which would matter for an unpaginated-by-default feed.

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 sentences with no filler, and the purpose is front-loaded before the pagination note. The second sentence is slightly redundant in wording ("nextCursor from the previous response's cursor"), but the overall structure is tight and appropriately sized.

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

Completeness3/5

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

With six optional parameters, no required inputs, and no output schema, the description should carry more weight: it never says what an activity record contains (id, type, amount, status) or how the status filter behaves, which an agent needs since no output schema documents the return shape. It is adequate for selecting the tool but thin for interpreting results.

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 coverage is 50%: since/until/profileId are documented in-schema, while size, status (the enum) and nextCursor are not. The description does add real meaning for nextCursor by explaining it must come from the previous response's cursor, which is a genuine chaining constraint beyond the type. The "recent" framing hints at recency scoping, but size and the status enum values remain unexplained.

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 and resource ("List recent account activity") and enumerates the concrete activity types returned (card spend, transfers, conversions, top-ups), so an agent knows this is the broad activity feed. It does not distinguish itself from the narrower wise_list_transfers or wise_get_balance_statement siblings, so it stops short of a 5.

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?

The only usage instruction is how to paginate. There is no statement of when to prefer this broad feed over wise_list_transfers, nor any prerequisite about profileId (the schema mentions the WISE_PROFILE_ID env fallback, but the description does not). The agent must infer the routing decision.

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