Luno MCP Server

Official

Overview Schema Source Related Servers Discussions(1)Admin

list_transactions

Read-onlyIdempotent

Retrieve paginated ledger entries for a specific account to support reconciliation, exports, and audit trails. Advance min_row to iterate through all rows.

Instructions

List ledger entries for a single account on the authenticated profile, paginated by row ID. min_row is inclusive, max_row is exclusive, and the API caps a single window at 1000 rows. Requires API credentials. Use for reconciliation, exports, or audit trails; iterate by advancing min_row to (last returned row + 1).

Input Schema

TableJSON Schema

Name	Required	Description
`account_id`	Yes	Numeric account ID, as a string (from get_balances).
`max_row`	No	Last row to return, exclusive. Defaults to 100 when omitted. The Luno API caps (max_row - min_row) at 1000.
`min_row`	No	First row to return, inclusive (1-based). Defaults to 1 when omitted.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`transactions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.6.3May 27, 2026
Removedv0.6.2May 22, 2026

Changed8 schema fields changedv0.6.1May 19, 2026

changedInput schema / properties / account_id / description

Previous value: -"Account ID"New value: +"Numeric account ID, as a string (from get_balances)."

addedInput schema / properties / max_row / default
```
Added value: +100
```

changedInput schema / properties / max_row / description

Previous value: -"Maximum row ID to return (for pagination, exclusive)"New value: +"Last row to return, exclusive. Defaults to 100 when omitted. The Luno API caps (max_row - min_row) at 1000."

addedInput schema / properties / max_row / minimum
```
Added value: +1
```
addedInput schema / properties / min_row / default
```
Added value: +1
```

changedInput schema / properties / min_row / description

Previous value: -"Minimum row ID to return (for pagination, inclusive)"New value: +"First row to return, inclusive (1-based). Defaults to 1 when omitted."

addedInput schema / properties / min_row / minimum
```
Added value: +1
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "transactions": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "account_id": {
+            "type": "string"
+          },
+          "available": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "available_delta": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "balance": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "balance_delta": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "currency": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "detail_fields": {
+            "additionalProperties": false,
+            "properties": {
+              "crypto_details": {
+                "additionalProperties": false,
+                "properties": {
+                  "address": {
+                    "type": "string"
+                  },
+                  "txid": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "address",
+                  "txid"
+                ],
+                "type": "object"
+              },
+              "trade_details": {
+                "additionalProperties": false,
+                "properties": {
+                  "pair": {
+                    "type": "string"
+                  },
+                  "price": {
+                    "additionalProperties": false,
+                    "properties": {},
+                    "type": "object"
+                  },
+                  "sequence": {
+                    "type": "integer"
+                  },
+                  "volume": {
+                    "additionalProperties": false,
+                    "properties": {},
+                    "type": "object"
+                  }
+                },
+                "required": [
+                  "pair",
+                  "price",
+                  "sequence",
+                  "volume"
+                ],
+                "type": "object"
+              }
+            },
+            "required": [
+              "crypto_details",
+              "trade_details"
+            ],
+            "type": "object"
+          },
+          "details": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "reference": {
+            "type": "string"
+          },
+          "row_index": {
+            "type": "integer"
+          },
+          "timestamp": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          }
+        },
+        "required": [
+          "account_id",
+          "available",
+          "available_delta",
+          "balance",
+          "balance_delta",
+          "currency",
+          "description",
+          "detail_fields",
+          "details",
+          "kind",
+          "reference",
+          "row_index",
+          "timestamp"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "transactions"
+  ],
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

A4.7/5.0

Behavior5/5

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

The description adds significant behavioral details beyond annotations: pagination by row ID with inclusive/exclusive bounds, API cap of 1000 rows per window, and credential requirements. There is no contradiction with the readOnlyHint and other annotations.

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?

The description is a single paragraph with three sentences, each serving a purpose: stating the main function, explaining pagination mechanics, and suggesting usage. No redundant 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?

The description covers the core behavior, pagination constraints, and use cases. With an output schema assumed to exist, the description sufficiently prepares an agent for correct invocation without needing further external knowledge.

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?

Schema coverage is 100%, so baseline is 3. The description adds value by explaining inclusivity/exclusivity of rows, the API cap, and default values. It also clarifies account_id as a numeric string from get_balances.

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 clearly states it lists ledger entries for a single account on the authenticated profile, paginated by row ID. This distinguishes it from siblings like list_orders or list_trades which target different resources.

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 description provides explicit use cases: reconciliation, exports, or audit trails. It also explains the pagination iteration pattern. However, it does not explicitly state when not to use it or list alternatives.

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

Deploy Server