Skip to main content
Glama

search_decisions_citing

Read-onlyIdempotent

Court decisions that EXPLICITLY cite an article ("article 1240 du code civil", "art. L. 1152-1 du code du travail"). Does not find indirect references or citations without an article number: searching by concept is for search.

Example: search_decisions_citing(code="CC", num="1240")

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": {
      "code": "<code>",
      "num": "<num>"
    },
    "name": "search_decisions_citing"
  }
}

Input Schema

NameRequiredDescriptionDefault
numYesarticle number (e.g. "L1152-1", "1240")
codeYesas in get_law_article (abbreviation, name or LEGITEXT)
limitNonumber of decisions per source (default 20, max 50)
sourcesNooptional list of sources to query among ["dila", "jade", "cedh", "cjue"]. Default: all. "jade" = administrative courts: JADE + the TA/CAA/CE open data (15/11/2026).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / sources / description
      Previous value: -"optional list of sources to query among [\"dila\", \"jade\", \"cedh\", \"cjue\"]. Default: all."New value: +"optional list of sources to query among [\"dila\", \"jade\", \"cedh\", \"cjue\"]. Default: all. \"jade\" = administrative courts: JADE + the TA/CAA/CE open data (15/11/2026)."
  2. Changed4 schema fields changed
    • changedInput schema / properties / code / description
      Previous value: -"comme get_law_article (sigle, nom ou LEGITEXT)"New value: +"as in get_law_article (abbreviation, name or LEGITEXT)"
    • changedInput schema / properties / limit / description
      Previous value: -"nombre de décisions par source (défaut 20, max 50)"New value: +"number of decisions per source (default 20, max 50)"
    • changedInput schema / properties / num / description
      Previous value: -"numéro de l'article (ex : \"L1152-1\", \"1240\")"New value: +"article number (e.g. \"L1152-1\", \"1240\")"
    • changedInput schema / properties / sources / description
      Previous value: -"liste optionnelle de sources à interroger parmi [\"dila\", \"jade\", \"cedh\", \"cjue\"]. Par défaut : toutes."New value: +"optional list of sources to query among [\"dila\", \"jade\", \"cedh\", \"cjue\"]. Default: all."
  3. Changed1 schema field changed
    • changedInput schema / properties / code / description
      Previous value: -"code court de l'article (ex : \"CT\", \"CC\")"New value: +"comme get_law_article (sigle, nom ou LEGITEXT)"
  4. Changed4 schema fields changed
    • addedInput schema / properties / code / description
      Added value: +"code court de l'article (ex : \"CT\", \"CC\")"
    • addedInput schema / properties / limit / description
      Added value: +"nombre de décisions par source (défaut 20, max 50)"
    • addedInput schema / properties / num / description
      Added value: +"numéro de l'article (ex : \"L1152-1\", \"1240\")"
    • addedInput schema / properties / sources / description
      Added value: +"liste optionnelle de sources à interroger parmi [\"dila\", \"jade\", \"cedh\", \"cjue\"]. Par défaut : toutes."
  5. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: matching is literal on explicit article citations only, which tells the agent why results may be empty for conceptual queries. It does not discuss result volume or per-source merging, but the output schema covers return shape.

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?

Two short sentences plus one example, with the positive definition front-loaded, followed by the exclusion and the alternative. No redundant restatement of the tool name or schema fields.

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 a rich annotation set, full schema coverage, and an output schema, the description supplies what remains: the precise matching semantics and the alternative tool. Only the interplay of limit and the four sources is left entirely to the schema, which is acceptable.

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%, so num, code, limit, and sources are already documented, including the source enum list and the max-50 limit. The example (code="CC", num="1240") illustrates the expected value shape but adds little beyond the schema's own descriptions; 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 and resource: court decisions that EXPLICITLY cite a given article, with concrete citation formats ("article 1240 du code civil"). It explicitly carves out the sibling `search` for concept-based lookup, so an agent can distinguish the two 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 Guidelines5/5

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

Gives both a when-to-use and a when-not-to-use: it does not find indirect references or citations lacking an article number, and names `search` as the alternative for concept queries. This is exactly the routing guidance needed among siblings like `search`, `search_case_law`, and `get_law_article`.

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