Skip to main content
Glama

Mandate Office

by com.mandateoffice
OverviewDiscussionsAdmin

find_law

Read-only

Find EU or national legislation by title words, abbreviation or number in one call. Returns compact items with stable id, official links (EUR-Lex/ELI/CELEX or the national official portal), title, date, source, source_url and retrieved_at. Every item has status (in_force | repealed | unknown; in_force only when the official source says so), consolidated_url (current consolidated text, or null when the source has none), checked_at (date the status was read) and status_source. Search: EU (CELLAR, 24 languages via lang) and DE, EE, ES, AT, NL, PL, DK, LU, SE, IE, IT, LT, FI, CZ, HR, LV, SI, FR. France (Légifrance): codes and consolidated laws by title or number (e.g. '78-17'), article text by ' article ' (e.g. 'Code civil article 1240'), and French case law (JUDILIBRE, Cour de cassation) with a 'juri:' prefix (e.g. 'juri:clause de non-concurrence'). Other EU Member States: returns the official portal, its search link and ELI pattern (link_only). Free, read-only, no API key during beta. No legal advice.

Input Schema

NameRequiredDescriptionDefault
langNoEU only: two-letter language of the title and EUR-Lex link, default en.
limitNo1-25, default 10.
queryYesTitle words, abbreviation or number, e.g. 'general data protection', '2016/679', 'GmbHG', 'Äriseadustik', 'sociedades de capital'.
countryNoEU (default) or an EU Member State ISO code. Search: EU, DE, EE, ES, AT, NL, PL, DK, LU, SE, IE, IT, LT, FI, CZ, HR, LV, SI, FR; all 27 Member States return at least official portal links.
in_force_onlyNoDefault true (EU, ES). EE results are always the acts in force today.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"EU (default) or an EU Member State ISO code. Search: EU, DE, EE, ES, AT, NL, PL, DK, LU, SE, IE, IT, LT, FR; all 27 Member States return at least official portal links."New value: +"EU (default) or an EU Member State ISO code. Search: EU, DE, EE, ES, AT, NL, PL, DK, LU, SE, IE, IT, LT, FI, CZ, HR, LV, SI, FR; all 27 Member States return at least official portal links."
  2. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"EU (default) or an EU Member State ISO code. Search: EU, DE, EE, ES, AT, NL, PL, DK, LU, SE, IE, IT, LT; all 27 Member States return at least official portal links."New value: +"EU (default) or an EU Member State ISO code. Search: EU, DE, EE, ES, AT, NL, PL, DK, LU, SE, IE, IT, LT, FR; all 27 Member States return at least official portal links."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only and open-world, but the description adds the return shape, status semantics ('in_force only when the official source says so'), consolidated_url null meaning, checked_at/status_source provenance, and the link_only behavior for unindexed Member States. This is exactly the behavioral detail an agent needs 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with purpose and return contract, then drills into country-specific behavior. The single dense paragraph is information-rich but would scan better with light structural separation of search coverage versus return semantics.

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?

There is no output schema, so the description must carry the return contract, and it does: ids, links, status fields, provenance, and null semantics. Coverage of the supported jurisdictions and the French special cases completes what an agent needs to call it correctly; limit bounds are already in the schema.

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 100%, so the baseline is 3, but the description adds real query semantics not in the schema: '78-17', '<code> article <n>' article text, and the 'juri:' case-law prefix. Country coverage and the in_force_only caveats are reinforced rather than newly explained, keeping it below a 5.

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 first sentence states a specific verb and resource ('Find EU or national legislation') plus the query modes (title words, abbreviation, number) and the 'in one call' scope. An agent can distinguish this search tool from the link-retrieval sibling get_law_link 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 Guidelines4/5

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

It gives clear context on when this applies: EU-wide and specific national searches, French code/article/case-law syntax, and 'link_only' fallback for other Member States. It does not explicitly name when to use get_law_link or list_sources instead, so sibling routing is left implicit.

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