Skip to main content
Glama

Fr Judilibre Taxonomy

fr_judilibre_taxonomy
Read-onlyIdempotent

Resolve the short codes fr_judilibre_search/fr_judilibre_decision use (jurisdiction, chamber, formation, type, solution, publication, theme) into their French labels, or the reverse (a label into its code). Pass no id to list the available taxonomy categories.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "jurisdiction"
    },
    "name": "fr_judilibre_taxonomy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoTaxonomy category, e.g. "jurisdiction", "chamber", "formation", "type", "solution", "publication", "theme". Omit to list the categories.
keyNoA code within `id` to resolve to its label, e.g. id:"jurisdiction", key:"cc" -> "Cour de cassation". Requires `id`.
valueNoA label within `id` to resolve back to its code (the reverse of `key`). Requires `id`.
context_valueNoContext needed by some categories, e.g. "chamber" only makes sense within a jurisdiction: context_value:"cc" for the Cour de cassation's chambers (the default), "ca" for a cour d'appel's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context_value / description
      Previous value: -"Context needed by some categories — e.g. \"chamber\" only makes sense within a jurisdiction: context_value:\"cc\" for the Cour de cassation's chambers (the default), \"ca\" for a cour d'appel's."New value: +"Context needed by some categories, e.g. \"chamber\" only makes sense within a jurisdiction: context_value:\"cc\" for the Cour de cassation's chambers (the default), \"ca\" for a cour d'appel's."
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so safety is covered. The description adds behavioral detail beyond that: bidirectional resolution (code→label and label→code) and the no-`id` listing mode. It doesn't mention error handling, whether results are cached, or the 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.

Conciseness4/5

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

Effectively one dense sentence plus a sentence on listing; both front-load the primary action and the fallback mode. The parenthetical category list is slightly heavy but earns its place as the accepted `id` values, which are not enumerated in the schema.

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?

For a small read-only lookup tool with full schema coverage, the description covers the two directions of resolution and the category-listing mode. With no output schema, it could state the result shape more explicitly (single label string vs object), but the intent is inferable.

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 all four parameters including the `key`/`value` symmetry and `context_value` example are already documented in the schema. The description's parameter content mostly restates the category names and the omit-`id` rule, adding little beyond the schema baseline.

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 (resolve) and resource (taxonomy short codes) and explicitly ties its role to the siblings fr_judilibre_search and fr_judilibre_decision as the consumers of those codes. An agent can tell this is a code/label lookup utility distinct from the search and decision tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Implies usage (translate codes returned by the search/decision tools, or go from label to code) and gives one concrete mode: omit `id` to list categories. It does not state when not to use it, nor what happens with an unknown code/label.

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.