Payments Law EU

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.

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

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses the ranked-candidate behavior, the three confidence tiers (exact/strong/ambiguous, with precise definitions), and the handling of citations for instruments outside the corpus: those are named with CELEX and ELI rather than guessed. This is substantial behavioral context not present in the annotations.

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?

The description is three dense sentences with no filler. The primary instruction and usage boundary come first, followed by output behavior and edge-case handling. Every sentence adds information that the schema and annotations do not already provide.

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?

Given the read-only/idempotent annotations, an output schema, and a single required citation parameter, the description covers the key operational details: what inputs look like, how results are ranked and scored, how ambiguity is surfaced, and what happens for out-of-corpus citations. Nothing essential for calling this tool correctly appears to be missing.

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%, and the description does not explain the limit or cursor parameters. However, the central citation parameter is well illustrated with concrete forms, and the description ties the citation to the output semantics (instrument and provision locator). The two undocumented parameters are generic pagination controls whose purposes are largely self-evident, so the gap is minor.

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 opens with a concrete verb and resource: 'resolve a written EU legal citation ... into an instrument and provision locator,' and gives a real example (Article 97(1) PSD2). It also distinguishes itself from search_legislation by stating that search_legislation handles topics rather than citations.

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?

It explicitly states when to use the tool ('Use this to resolve a written EU legal citation') and when not to ('For a topic rather than a citation, use search_legislation'). This gives an agent a clear decision rule instead of leaving the alternative inference to sibling names.

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?