Payments Law — EU payments legislation

Resolve an EU legal citation

resolve_citation

Read-onlyIdempotent

Use this to resolve a written EU legal citation, such as Article 97(1) PSD2, into an instrument and provision locator. For a topic rather than a citation, use search_legislation. Ranked candidates with ambiguity flagged and confidence stated: exact (instrument certain, provision found), strong (instrument certain, provision not verified or not named) or ambiguous (more than one reading). A citation of an instrument this corpus does not hold is named, with its CELEX and ELI, rather than guessed at.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`cursor`	No
`citation`	Yes	A citation in any form a reader would write: "Article 97(1) PSD2", "Art. 5a of Regulation (EU) No 910/2014", a CELEX number, an ELI path, or a bare acronym.

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.

Changed2 schema fields changedOct 4, 2026

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"
-]
```

Changed4 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"
+]
```

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "ambiguous": {
-        "type": "boolean"
-      },
-      "items": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "cite": {
-              "type": "string"
-            },
-            "confidence": {
-              "enum": [
-                "exact",
-                "strong",
-                "ambiguous"
-              ],
-              "type": "string"
-            },
-            "instrument_id": {
-              "type": "string"
-            },
-            "kind": {
-              "type": "string"
-            },
-            "locator": {
-              "anyOf": [
-                {
-                  "additionalProperties": {},
-                  "propertyNames": {
-                    "type": "string"
-                  },
-                  "type": "object"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "url": {
-              "type": "string"
-            },
-            "why": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "instrument_id",
-            "cite",
-            "kind",
-            "locator",
-            "confidence",
-            "why",
-            "url"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "not_in_corpus": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "celex": {
-              "anyOf": [
-                {
-                  "type": "string"
-                },
-                {
-                  "type": "null"
-                }
-              ]
-            },
-            "named": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "named",
-            "celex"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "total": {
-        "type": "number"
-      },
-      "unresolved": {
-        "type": "boolean"
-      }
-    },
-    "required": [
-      "items",
-      "next_cursor",
-      "total",
-      "ambiguous",
-      "unresolved",
-      "not_in_corpus"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "ambiguous": {
+        "type": "boolean"
+      },
+      "items": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "cite": {
+              "type": "string"
+            },
+            "confidence": {
+              "enum": [
+                "exact",
+                "strong",
+                "ambiguous"
+              ],
+              "type": "string"
+            },
+            "instrument_id": {
+              "type": "string"
+            },
+            "kind": {
+              "type": "string"
+            },
+            "locator": {
+              "anyOf": [
+                {
+                  "additionalProperties": {},
+                  "propertyNames": {
+                    "type": "string"
+                  },
+                  "type": "object"
+                },
+                {
+                  "type": "null"
+                }
+              ]
+            },
+            "url": {
+              "type": "string"
+            },
+            "why": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "instrument_id",
+            "cite",
+            "kind",
+            "locator",
+            "confidence",
+            "why",
+            "url"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "next_cursor": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "not_in_corpus": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "celex": {
+              "type": [
+                "string",
+                "null"
+              ]
+            },
+            "named": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "named",
+            "celex"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "total": {
+        "type": "number"
+      },
+      "unresolved": {
+        "type": "boolean"
+      }
+    },
+    "required": [
+      "items",
+      "next_cursor",
+      "total",
+      "ambiguous",
+      "unresolved",
+      "not_in_corpus"
+    ],
+    "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 read-only, idempotent, closed-world behavior, so safety is covered. The description adds genuinely new behavior: ranked candidates, a three-level confidence taxonomy (exact / strong / ambiguous), explicit ambiguity flagging, and the fallback that a citation outside the corpus is returned with CELEX and ELI rather than guessed. It does not mention pagination behavior, which is the only notable omission.

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 the purpose, then the routing rule, then the result contract — no filler. The confidence-taxonomy sentence is tightly packed but each clause carries distinct information.

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?

Given an output schema exists, the description need not spell out return values, yet it usefully characterizes the shape (ranked candidates, ambiguity, confidence) and the edge case of instruments absent from the corpus. The remaining gap is pagination guidance for limit/cursor, which matters for a tool that can return ranked candidate sets.

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 coverage is only 33%: 'limit' and 'cursor' have no description in either the schema or the description, leaving pagination semantics undocumented. For the one documented parameter, the description's example (“Article 97(1) PSD2”) largely duplicates what the schema already lists, so it does not compensate for the coverage gap.

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 precise verb + resource + transformation: resolve a written EU legal citation into an instrument and provision locator. It also names the sibling it is not (search_legislation), so an agent can separate it from the topic-search tool 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 Guidelines5/5

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

Explicitly gives the use case (a written citation such as "Article 97(1) PSD2") and the exclusion with a named alternative ("For a topic rather than a citation, use search_legislation"). The condition that selects the alternative is stated, not left to inference.

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?