Skip to main content
Glama

EU law lookup (free)

eu_law_lookup
Read-onlyIdempotent

Free. Use when the user cites an EU regulation, directive or decision and you need its official title, date, whether it is still in force, and the EUR-Lex link to cite: by CELEX number (e.g. 32016R0679) or citation (e.g. Regulation (EU) 2016/679, Directive 2015/849).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "celex": "<celex>"
    },
    "name": "eu_law_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
celexYesCELEX number or a citation like 'Regulation (EU) 2016/679'

Output Schema

NameRequiredDescriptionDefault
urlNoEUR-Lex link
celexNoCELEX number
titleNoOfficial title
sourceNoSources to cite
in_forceNoWhether it is in force

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "celex": {
      +      "description": "CELEX number"
      +    },
      +    "in_force": {
      +      "description": "Whether it is in force"
      +    },
      +    "source": {
      +      "description": "Sources to cite"
      +    },
      +    "title": {
      +      "description": "Official title"
      +    },
      +    "url": {
      +      "description": "EUR-Lex link"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds useful context: it is free, it resolves in-force status (a substantive behavioral trait), and it enumerates the returned fields. It does not mention failure behavior for invalid or unknown CELEX numbers, keeping it from a 5.

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?

A single sentence, front-loaded with cost ('Free'), then the use condition, then accepted input formats. Every clause carries information; no 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?

A one-parameter, read-only lookup with an output schema and full annotation coverage. The description supplies the use trigger and the input format variants, which is everything needed to invoke it correctly.

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 coverage is 100% and the schema property already documents both accepted forms (CELEX number or citation). The description reinforces this with a concrete CELEX example (32016R0679) and two citation examples, which is marginally additive but largely repeats structured data. Baseline 3 applies.

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 (lookup) and resource (EU regulation, directive, decision) plus exactly what it returns: official title, date, in-force status, and EUR-Lex link. No sibling tool overlaps this domain, so the scope is unambiguous.

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 trigger condition is explicit: 'Use when the user cites an EU regulation, directive or decision and you need its official title, date, whether it is still in force, and the EUR-Lex link to cite.' No alternatives are named, but none exist among the siblings, so this leaves little to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources