Payments Law — EU payments legislation

Discover held EU legislation

list_instruments

Read-onlyIdempotent

Use this to discover which EU instruments are held before a coverage question, or find their registry ids and legal status. Paginated, filterable by status, category, core/supplementary, and by whether an instrument was in force on a given date. For corpus-coverage questions, filter by category here, enumerate each instrument with list_provisions, then open what you need with get_provision.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`cursor`	No
`status`	No	Legal status at the release, e.g. "in_force".
`is_core`	No
`category`	No
`in_force_on_date`	No	ISO date; keeps instruments in force on that date.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`error`	Yes
`coverage`	Yes
`warnings`	Yes
`pagination`	Yes
`provenance`	Yes
`derivations`	Yes
`corpus_release`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedOct 4, 2026

addedInput schema / properties / category / anyOf

Added value: +[
+  {
+    "maxLength": 64,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / category / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedInput schema / properties / cursor / anyOf

Added value: +[
+  {
+    "maxLength": 512,
+    "pattern": "^[A-Za-z0-9_-]+$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / cursor / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedInput schema / properties / in_force_on_date / anyOf

Added value: +[
+  {
+    "maxLength": 32,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / in_force_on_date / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

addedInput schema / properties / status / anyOf

Added value: +[
+  {
+    "maxLength": 64,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedInput schema / properties / status / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

Changed12 schema fields changedSep 20, 2026

removedInput schema / properties / category / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / category / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / cursor / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / cursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / in_force_on_date / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / in_force_on_date / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedInput schema / properties / is_core / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / is_core / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedInput schema / properties / status / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / status / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "items": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "instrument_id": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "instrument_id"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "total": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "items",
-      "next_cursor",
-      "total"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "items": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "instrument_id": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "instrument_id"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "next_cursor": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "total": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "items",
+      "next_cursor",
+      "total"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / pagination / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "complete": {
-        "type": "boolean"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "total": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "complete",
-      "next_cursor"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "complete": {
+        "type": "boolean"
+      },
+      "next_cursor": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "total": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "complete",
+      "next_cursor"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false and closed-world scope, so safety is covered. The description adds the meaningful behavioral detail that results are paginated and filterable, though it says nothing about result size limits or ordering.

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?

Three sentences, front-loaded with purpose then filters then workflow; every sentence earns its place. The final workflow sentence is somewhat dense but is the highest-value content.

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?

An output schema exists so return shape needn't be explained, and annotations carry the safety profile. Combined with the handoff workflow, the description is sufficient for correct invocation; only enum-like filter values are left implicit.

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 description coverage is only 33%, but the description compensates by naming the filter dimensions — status, category, core/supplementary, in-force-on-date — which map onto four of the six parameters, and 'Paginated' signals limit/cursor usage. It stops short of giving value formats (e.g. valid category values).

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?

States a specific verb and resource ('discover which EU instruments are held') plus the secondary affordances (registry ids, legal status). It also names the siblings it hands off to (list_provisions, get_provision), so an agent can separate it from the other list/search tools without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use ('before a coverage question'), explicit filtering conditions, and a concrete multi-tool workflow for corpus-coverage questions. It tells the agent not just what this tool does but where it sits in a sequence with alternatives.

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

All Payments Law — EU payments legislation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?