Payments Law EU

Read legislative source notes

get_source_notes

Read-onlyIdempotent

Use this to read the original legislative footnotes and source-note bodies for a held instrument, including preamble and annex notes. Omit note_key for the paginated inventory; supply an exact returned key to retrieve one. Keys retain source scope because printed markers may repeat. This tool does not infer ownership by a provision. Historical versions return an explicit version_not_served link.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Notes per page, default 10; complete bodies are never truncated.
`cursor`	No	Continue with the same arguments; bound to this corpus release.
`note_key`	No	Exact key returned by this tool. Omit to list notes. Printed markers may be reused and are not necessarily unique keys.
`version_id`	No	Omit or use current for the served version; pinned versions return an explicit version_not_served link.
`instrument_id`	Yes	Registry instrument id.

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.

Changed6 schema fields changedSep 20, 2026

removedInput schema / properties / cursor / anyOf

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

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

removedInput schema / properties / version_id / anyOf

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

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

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "instrument_id": {
-        "type": "string"
-      },
-      "items": {
-        "items": {
-          "additionalProperties": false,
-          "properties": {
-            "instrument_id": {
-              "type": "string"
-            },
-            "marker": {
-              "type": "string"
-            },
-            "note_key": {
-              "type": "string"
-            },
-            "text": {
-              "type": "string"
-            },
-            "url": {
-              "type": "string"
-            },
-            "version_id": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "instrument_id",
-            "version_id",
-            "note_key",
-            "marker",
-            "text",
-            "url"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "total": {
-        "type": "number"
-      },
-      "version_id": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "instrument_id",
-      "version_id",
-      "items",
-      "total",
-      "next_cursor"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "instrument_id": {
+        "type": "string"
+      },
+      "items": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "instrument_id": {
+              "type": "string"
+            },
+            "marker": {
+              "type": "string"
+            },
+            "note_key": {
+              "type": "string"
+            },
+            "text": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            },
+            "version_id": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "instrument_id",
+            "version_id",
+            "note_key",
+            "marker",
+            "text",
+            "url"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "next_cursor": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "total": {
+        "type": "number"
+      },
+      "version_id": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "instrument_id",
+      "version_id",
+      "items",
+      "total",
+      "next_cursor"
+    ],
+    "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"
+  }
+]

AddedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnly and idempotent behavior, and the description adds non-obvious details: keys retain source scope because printed markers repeat, no ownership inference occurs, and historical versions return an explicit version_not_served link. These are valuable behavioral disclosures beyond the structured fields.

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?

Four short sentences, each with a distinct job: purpose, pagination mode, key semantics, and version caveat. There is no filler or repetition of schema content.

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?

With an output schema present and annotations covering read-only/idempotent semantics, the description sufficiently covers purpose, pagination, note_key usage, version behavior, and a known limitation. Nothing material is missing for correct invocation.

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 100%, so the baseline is 3. The description goes further by clarifying note_key semantics (omit for inventory, supply exact returned key, printed markers may repeat) and version_id behavior (historical versions return version_not_served link), adding genuine meaning beyond the schema.

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 names a specific verb ('read') and a specific resource ('original legislative footnotes and source-note bodies'), including preamble and annex notes. This clearly distinguishes it from sibling tools like get_provision, get_instrument, and search_legislation.

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?

It gives clear usage context: use for source notes of a held instrument, with two modes (paginated inventory vs. single note by exact key). It also adds an exclusion ('does not infer ownership by a provision'), though it does not explicitly name alternative sibling tools.

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?