Payments Law EU

Find EU legislative definitions

search_defined_terms

Read-onlyIdempotent

Use this to find which EU instruments define a legal term, such as payment transaction or payment account, and where their definitions differ. For definition wording use get_defined_term. A listing: term, definers and divergence flags, with no definition text. Matching is over the term itself, never the definition body. Divergence is judged on the RESOLVED text as well as the verbatim one, because several instruments defining a term by pointing at the same root agree, however differently their pointers read. Pass only_divergent to find where the corpus does not agree with itself.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No
`query`	No	Term text to match. Matching is over the TERM only, never the definition body. Omit for the full alphabetical listing of every term the corpus defines.
`cursor`	No
`instrument`	No	Keep only terms defined in this instrument, e.g. "psd-2".
`only_divergent`	No	Keep only terms whose definers disagree — on the resolved text, the verbatim text, or both.

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.

Changed10 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 / instrument / anyOf

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

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

removedInput schema / properties / only_divergent / anyOf

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

addedInput schema / properties / only_divergent / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```

removedInput schema / properties / query / anyOf

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

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

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "additionalProperties": {},
-    "properties": {
-      "items": {
-        "items": {
-          "additionalProperties": {},
-          "properties": {
-            "defined_in": {
-              "items": {
-                "additionalProperties": {},
-                "properties": {
-                  "cite": {
-                    "type": "string"
-                  },
-                  "defined_within": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  },
-                  "instrument_id": {
-                    "type": "string"
-                  },
-                  "qualifier": {
-                    "anyOf": [
-                      {
-                        "type": "string"
-                      },
-                      {
-                        "type": "null"
-                      }
-                    ]
-                  }
-                },
-                "required": [
-                  "instrument_id",
-                  "qualifier",
-                  "defined_within",
-                  "cite"
-                ],
-                "type": "object"
-              },
-              "type": "array"
-            },
-            "divergent_resolved": {
-              "type": "boolean"
-            },
-            "divergent_verbatim": {
-              "type": "boolean"
-            },
-            "term": {
-              "type": "string"
-            }
-          },
-          "required": [
-            "term",
-            "defined_in",
-            "divergent_verbatim",
-            "divergent_resolved"
-          ],
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "total": {
-        "type": "number"
-      }
-    },
-    "required": [
-      "items",
-      "next_cursor",
-      "total"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "properties": {
+      "items": {
+        "items": {
+          "additionalProperties": {},
+          "properties": {
+            "defined_in": {
+              "items": {
+                "additionalProperties": {},
+                "properties": {
+                  "cite": {
+                    "type": "string"
+                  },
+                  "defined_within": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  },
+                  "instrument_id": {
+                    "type": "string"
+                  },
+                  "qualifier": {
+                    "type": [
+                      "string",
+                      "null"
+                    ]
+                  }
+                },
+                "required": [
+                  "instrument_id",
+                  "qualifier",
+                  "defined_within",
+                  "cite"
+                ],
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "divergent_resolved": {
+              "type": "boolean"
+            },
+            "divergent_verbatim": {
+              "type": "boolean"
+            },
+            "term": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "term",
+            "defined_in",
+            "divergent_verbatim",
+            "divergent_resolved"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "next_cursor": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "total": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "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.9/5.0

Behavior5/5

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

Even though annotations already declare readOnlyHint and idempotentHint, the description adds meaningful behavioral detail: no definition text is returned, matching is restricted to the term field, and divergence is judged on both resolved and verbatim text. The explanation about instruments pointing at the same root is valuable context beyond 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 compact and front-loaded with purpose, then alternatives, output shape, matching behavior, and a key divergence nuance. Every sentence contributes unique information without repetition or filler.

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 output schema exists and annotations cover safety and idempotency, the description is sufficient for correct invocation. It states what the result contains, how matching works, how divergence is computed, and when to use only_divergent. No essential decision for the agent is left unaddressed.

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 coverage is 60%, and the description reinforces the meanings of query and only_divergent, including the resolved-versus-verbatim nuance. It does not explain limit or cursor, but these are conventional pagination parameters and the schema provides partial descriptions for the main filters.

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 specific verb and resource: 'find which EU instruments define a legal term' and explicitly names the output as a listing with term, definers, and divergence flags. It also distinguishes itself from the sibling get_defined_term by saying 'For definition wording use get_defined_term.' This leaves no ambiguity about what the tool does.

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?

The description gives clear use context, tells the agent when to prefer get_defined_term instead, and clarifies that matching is over the term only, never the definition body. It also instructs to 'Pass only_divergent' when looking for disagreement, giving an explicit condition for parameter use.

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?