Skip to main content
Glama

Mandate Office

by com.mandateoffice
OverviewDiscussionsAdmin

get_law_link

Read-only

Resolve one legal act id to its official links and title, with status (in_force | repealed | unknown), consolidated_url, checked_at and status_source. Accepts CELEX (32016R0679), EU ELI (eli/reg/2016/679/oj), BOE id (BOE-A-2015-10566), de: (de:GmbHG), article/section level ('BOE-A-2000-323#a647', 'BOE-A-1862-4073 art 17 ter', 'de:ZVG § 71', or the article argument), ee:rt:, French ids (fr:LEGIARTI… article text, fr:LEGITEXT… code with article argument, fr:JORFTEXT…, 'fr:Code civil art 1240', fr:juri: full decision), and national ids ':' as returned by find_law (e.g. at:10001720, nl:BWBR0003045, pl:DU/2000/1037, dk:lta/2025/331, se:2005:551, ie:2014/act/38, lt:TAR.8A39C83848CB). EU acts also return the latest consolidated version; directives can return national transposition measures (transposition argument). Free, read-only.

Input Schema

NameRequiredDescriptionDefault
idYesCELEX, ELI, BOE id (optionally with article: 'BOE-A-2000-323#a647', 'BOE-A-1862-4073 art 17 ter'), de:<abbreviation> (optionally with section: 'de:ZVG § 71'), ee:rt:<Riigi Teataja id>, French ids (fr:LEGIARTI…, fr:LEGITEXT… with article, 'fr:Code civil art 1240', fr:juri:<JUDILIBRE id>), or a national id '<cc>:<id>' from find_law.
langNoEU only: two-letter language, default en.
articleNoOptional article or section: ES '647', '17 ter' (anchor read from the BOE page's table of contents); DE '§ 71', 'Art. 1'; FR '1240', 'L225-1' (with fr:LEGITEXT… or a code name; returns the article text in force today). Returned under article/section with a verified deep link.
transpositionNoEU directives only: true lists national transposition measures (NIM) for all Member States; a country code (e.g. 'EE') lists one country's measures. Consolidated versions are always returned for EU acts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / article / description
      Previous value: -"Optional article or section: ES '647', '17 ter' (anchor read from the BOE page's table of contents); DE '§ 71', 'Art. 1'. Returned under article/section with a verified deep link."New value: +"Optional article or section: ES '647', '17 ter' (anchor read from the BOE page's table of contents); DE '§ 71', 'Art. 1'; FR '1240', 'L225-1' (with fr:LEGITEXT… or a code name; returns the article text in force today). Returned under article/section with a verified deep link."
    • changedInput schema / properties / id / description
      Previous value: -"CELEX, ELI, BOE id (optionally with article: 'BOE-A-2000-323#a647', 'BOE-A-1862-4073 art 17 ter'), de:<abbreviation> (optionally with section: 'de:ZVG § 71'), ee:rt:<Riigi Teataja id>, or a national id '<cc>:<id>' from find_law."New value: +"CELEX, ELI, BOE id (optionally with article: 'BOE-A-2000-323#a647', 'BOE-A-1862-4073 art 17 ter'), de:<abbreviation> (optionally with section: 'de:ZVG § 71'), ee:rt:<Riigi Teataja id>, French ids (fr:LEGIARTI…, fr:LEGITEXT… with article, 'fr:Code civil art 1240', fr:juri:<JUDILIBRE id>), or a national id '<cc>:<id>' from find_law."
  2. Changed1 schema field changed
    • addedInput schema / properties / transposition
      Added value: +{
+  "description": "EU directives only: true lists national transposition measures (NIM) for all Member States; a country code (e.g. 'EE') lists one country's measures. Consolidated versions are always returned for EU acts.",
+  "type": [
+    "boolean",
+    "string"
+  ]
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / article
      Added value: +{
+  "description": "Optional article or section: ES '647', '17 ter' (anchor read from the BOE page's table of contents); DE '§ 71', 'Art. 1'. Returned under article/section with a verified deep link.",
+  "type": "string"
+}
    • changedInput schema / properties / id / description
      Previous value: -"CELEX, ELI, BOE id, or de:<abbreviation>."New value: +"CELEX, ELI, BOE id (optionally with article: 'BOE-A-2000-323#a647', 'BOE-A-1862-4073 art 17 ter'), de:<abbreviation> (optionally with section: 'de:ZVG § 71'), ee:rt:<Riigi Teataja id>, or a national id '<cc>:<id>' from find_law."
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful behavior: status values, consolidated_url, checked_at, status_source, consolidated versions for EU acts, and transposition measures for directives. It does not cover rate limits, error behavior, or authentication beyond "Free, read-only," but it substantially enriches the behavioral picture.

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?

The description is front-loaded with the core purpose and then enumerates supported formats. It is dense and lengthy, but the length is largely justified by the many id syntaxes the tool accepts; minor structural improvements could group the formats more clearly.

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?

With no output schema, the description carries the return-value burden and lists the key fields returned. It also explains EU consolidated versions and national transposition measures. It is complete enough for invocation, though it lacks detail on invalid-id or ambiguity handling.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all four parameters in detail. The description overlaps with the schema by listing accepted id formats and does not add much semantic meaning beyond those examples.

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 specific verb and resource: "Resolve one legal act id to its official links and title." It also names the returned status fields and distinguishes the tool from find_law by referencing national ids returned by find_law. An agent can tell what this tool does without opening the schema.

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?

The description gives extensive guidance on accepted id formats, including CELEX, ELI, BOE, French, and national ids from find_law. It does not explicitly say when to use this tool versus find_law or when not to use it, but the intended usage context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mandate Office toolsInspect
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