Payments Law EU

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

TableJSON Schema

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

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 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.3/5.0

Behavior4/5

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

Annotations provide read-only and idempotent hints; the description adds that results are metadata only, that articles/annexes are included by default, and that kind=recital is needed for recitals. This is meaningful behavioral context beyond annotations. It does not explain pagination/cursor semantics, but the output schema covers the return shape.

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 with no filler, front-loading the purpose and then delivering defaults and related-tool context. Every sentence earns its place.

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?

The description covers what the tool returns, how to invoke common variants, and how it connects to get_provision, with an output schema supplying return details. Pagination and filtering (cursor/limit/chapter) are not spelled out, so an agent may need to infer standard semantics; otherwise sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema descriptions are absent (0% coverage), so the description must carry the parameter documentation burden. It explains kind and its default and hints at topic via 'topic-tagged provisions', but leaves instrument_id format, chapter, limit, and cursor meaning/use undocumented. Self-descriptive names mitigate this somewhat, but the description does not fully compensate for the zero schema 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?

Uses an action verb 'browse' plus a concrete resource (EU instrument provisions), defines the scope (article, annex, recital index, topic-tagged provisions), and explicitly distinguishes itself from get_provision by noting each item carries the exact locator that tool accepts. This is specific enough for an agent to select it correctly.

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?

States the intended use case ('coverage question'), the default behavior ('Articles and annexes by default'), and the conditional for recitals ('pass kind=recital'). It also implicitly routes the agent: use this for metadata/indexing, then get_provision for the located provision. This gives clear directional guidance among siblings.

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 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?