Skip to main content
Glama

liens_droit_ue_france

Liens entre droit de l'UE et droit français. Sans numero : reference est un acte européen (CELEX, RGPD, « directive 2019/770 »...) et on obtient les textes et articles français qui le transposent ou le citent. Avec numero : reference est un code (« Code de la consommation ») et numero un article (« L217-4 ») : on obtient les actes européens liés. source : transposition (mesures déclarées à l'Union) ou mention (article qui cite l'acte). Liste non exhaustive : seuls sont recensés les rattachements déclarés à l'Union et les citations expresses.

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": {
      "reference": "<reference>"
    },
    "name": "liens_droit_ue_france"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
numeroNo
sourceNo
referenceYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does meaningful work: it explicitly warns that results are non-exhaustive, covering only declared transposition measures and express citations, which prevents an agent from treating an empty result as proof of no linkage. It also defines the semantics of the two `source` values. It does not mention result volume, pagination, or how `limite` affects output.

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 purpose is front-loaded and each subsequent clause earns its place: the two modes, the source values, then the coverage caveat. It is dense and unformatted, so the mode switch relies on the reader parsing 'Sans numero' / 'Avec numero' inline, but there is no filler.

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?

An output schema exists, so return values need not be explained, and the description covers the two critical things a caller needs: which input form triggers which direction, and the non-exhaustive nature of the corpus. The one substantive gap is the unexplained `limite` parameter for a tool that can return a list of texts.

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 0%, so the description must compensate, and it does for three of four parameters: `reference` is given dual, conditional semantics tied to `numero`, `numero` is illustrated with a concrete example ('L217-4'), and `source` is defined by its two accepted values. `limite` is never mentioned, leaving its effect and default of 15 undocumented anywhere.

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 opening sentence names the resource (links between EU law and French law) and the description then specifies precisely what the tool returns: French texts/articles that transpose or cite an EU act, or the EU acts linked to a given French article. The bidirectional framing makes it obviously distinct from siblings like rechercher_droit_ue or lire_texte_ue, which retrieve one side of the corpus rather than the linkage.

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 explicit conditional routing: 'Sans numero' invokes the EU-act-to-French-law direction, 'Avec numero' invokes the French-code-article-to-EU-act direction, with concrete examples of each input form. It also explains that the `source` value selects between transposition and mention. It stops short of naming alternative sibling tools or stating when not to use this one.

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.