Payments Law — EU payments legislation

Browse an instrument's provisions

list_provisions

Read-onlyIdempotent

Use this to browse an EU instrument's article, annex or recital index, or enumerate its topic-tagged provisions for a coverage question. Metadata only: each item carries the exact locator get_provision accepts. Articles and annexes by default; pass kind=recital for recitals.

Input Schema

Name	Required	Description	Default
`kind`	No
`limit`	No
`topic`	No
`cursor`	No
`chapter`	No
`instrument_id`	Yes

Output 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.

Changed1 schema field changedOct 14, 2026

changedInput schema / properties / instrument_id / pattern

Previous value: -"^[a-z0-9]+(?:-[a-z0-9]+)*$"New value: +"^[A-Za-z0-9]+(?:[ ._-][A-Za-z0-9]+)*$"

Changed8 schema fields changedOct 4, 2026

addedInput schema / properties / chapter / anyOf

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

removedInput schema / properties / chapter / 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 / instrument_id / maxLength
```
Added value: +64
```
addedInput schema / properties / instrument_id / pattern
```
Added value: +"^[a-z0-9]+(?:-[a-z0-9]+)*$"
```

addedInput schema / properties / topic / anyOf

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

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

Changed8 schema fields changedSep 20, 2026

removedInput schema / properties / chapter / anyOf

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

addedInput schema / properties / chapter / 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 / topic / anyOf

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

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

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "instrument_id": {
-        "type": "string"
-      },
-      "items": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "cite": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "cite"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "kinds_listed": {
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "total": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "instrument_id",
-      "kinds_listed",
-      "items",
-      "next_cursor",
-      "total"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "instrument_id": {
+        "type": "string"
+      },
+      "items": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "cite": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "cite"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "kinds_listed": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "next_cursor": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "total": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "instrument_id",
+      "kinds_listed",
+      "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.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds behavior the schema does not: the result is metadata only and the default kind is articles+annexes with recitals requiring kind=recital. Pagination/limit behavior is left unstated.

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?

Three tightly packed sentences: the use case first, then the metadata-only caveat and get_provision hand-off, then the kind default. Every sentence earns its place and nothing is repeated from the schema.

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 an output schema present, return values need not be described, and the description covers scope, default filtering and routing. The main residual gap is pagination (cursor/limit) and chapter filtering, which an agent may need when results are large.

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 0% across 6 parameters, so the description must compensate. It does explain the semantics of kind (including its default) and implies topic via 'topic-tagged provisions', but limit, cursor, chapter and the instrument_id format are left entirely undocumented in both places.

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?

Names a specific verb (browse/enumerate) and resource (an EU instrument's article, annex or recital index / topic-tagged provisions). It also implicitly distinguishes itself from get_provision by stating it returns metadata only, so an agent can tell the two apart without opening either schema.

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?

States when to reach for it ('for a coverage question', to browse an index) and names the downstream consumer, get_provision, whose accepted locator each item carries. There is no explicit when-not or exclusion, so it falls short of the full 5 but gives clear routing context.

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?