Skip to main content
Glama

Lexou · droit français

Trouver les juridictions compétentes d'une commune

trouver_juridictions
Read-onlyIdempotent

Tribunal judiciaire, tribunal de proximité, conseil de prud'hommes, tribunal de commerce, tribunal administratif et cour d'appel compétents pour une commune, avec leurs adresses, d'après la table officielle du ministère de la Justice. Pas pour choisir entre deux juridictions selon la nature du litige.

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_postal": "<code_postal>"
    },
    "name": "trouver_juridictions"
  }
}

Input Schema

NameRequiredDescriptionDefault
villeNoNom de la commune, utile quand un code postal couvre plusieurs communes
code_postalYesCode postal de la commune

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description's added value is modest: it reveals the authoritative source (table officielle du ministère de la Justice) and that addresses are included in the result. It says nothing about what happens when a postal code spans several communes (one result vs. many) or about result ordering.

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?

Two sentences with no filler: the first front-loads the returned resources and their source, the second delivers the exclusion. The enumeration of six court types is long but each item is meaningful for retrieval matching, so it earns its space.

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, two well-documented parameters and full annotation coverage, the description supplies what is needed: the scope, the source table, and the presence of addresses in the response. The only real gap is the ambiguity case of a postal code covering several communes, which the schema hints at but the description never resolves.

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 100% and the schema itself explains the ville/code_postal relationship ('utile quand un code postal couvre plusieurs communes') and the 5-digit pattern. The description adds no parameter-level detail, but with the schema doing that work and only two simple parameters, the baseline applies comfortably.

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 description names a specific verb (compétents pour une commune) and enumerates exactly which resources are returned: tribunal judiciaire, tribunal de proximité, conseil de prud'hommes, tribunal de commerce, tribunal administratif, cour d'appel, plus their addresses. An agent can tell immediately this is a lookup of competent courts for a location, not a calculation or a text lookup like the sibling tools.

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 an explicit when-not clause: 'Pas pour choisir entre deux juridictions selon la nature du litige,' which usefully rules out a plausible mis-call. It does not, however, name an alternative tool for that excluded case, so the agent must infer where to go instead — short of a 5.

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