Luno MCP Server

Official

Overview Schema Source Related Servers Discussions(1)Admin

list_orders

Read-onlyIdempotent

List open orders on your Luno profile, optionally filtered by trading pair, to review working orders before cancelling or placing new ones.

Instructions

List orders on the authenticated profile (open by default; recently completed orders may also appear depending on Luno API behaviour), optionally filtered by trading pair. Requires API credentials. Use this to inspect or audit working orders before cancelling them or placing new ones.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of orders to return (1-100). Defaults to 100.
`pair`	No	Optional trading pair filter (e.g. "XBTZAR"). Omit to list orders across all pairs.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`orders`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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

Changed7 schema fields changedv0.6.1May 19, 2026

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

changedInput schema / properties / limit / description

Previous value: -"Maximum number of orders to return (default: 100)"New value: +"Maximum number of orders to return (1-100). Defaults to 100."

addedInput schema / properties / limit / maximum
```
Added value: +100
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

changedInput schema / properties / pair / description

Previous value: -"Trading pair (e.g., XBTZAR)"New value: +"Optional trading pair filter (e.g. \"XBTZAR\"). Omit to list orders across all pairs."

addedInput schema / required
```
Added value: +[]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "orders": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "base": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "completed_timestamp": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "counter": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "creation_timestamp": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "expiration_timestamp": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "fee_base": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "fee_counter": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "limit_price": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "limit_volume": {
+            "additionalProperties": false,
+            "properties": {},
+            "type": "object"
+          },
+          "order_id": {
+            "type": "string"
+          },
+          "pair": {
+            "type": "string"
+          },
+          "state": {
+            "type": "string"
+          },
+          "time_in_force": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "base",
+          "completed_timestamp",
+          "counter",
+          "creation_timestamp",
+          "expiration_timestamp",
+          "fee_base",
+          "fee_counter",
+          "limit_price",
+          "limit_volume",
+          "order_id",
+          "pair",
+          "state",
+          "time_in_force",
+          "type"
+        ],
+        "type": "object"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    }
+  },
+  "required": [
+    "orders"
+  ],
+  "type": "object"
+}

First observedAug 15, 2025

TDQS

A4.3/5.0

Behavior4/5

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

Adds valuable behavioral context beyond annotations: open by default, possible inclusion of recently completed orders per Luno API behavior, and requirement for API credentials. Annotations already mark read-only, so no contradiction.

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, front-loaded with the core action. Every sentence adds value without redundancy.

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?

Given the presence of an output schema (not shown), the description adequately covers purpose, usage, behavior, and auth. No gaps for a listing tool.

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 100% with descriptions for both parameters. The description merely echoes the pair filter option without adding new meaning, meeting the baseline for high coverage.

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 states 'List orders on the authenticated profile' with optional pair filtering, clearly identifying the action and resource. It distinguishes from sibling tools like cancel_order or create_order by focusing on listing.

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?

Explicitly states when to use: 'inspect or audit working orders before cancelling them or placing new ones.' Does not provide when-not-to-use or alternatives, but context is clear.

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

Deploy Server