fr_judilibre_taxonomy

Pack: fr-judilibre · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/fr_judilibre_taxonomy for the schema, then POST the same URL with its arguments for the data.

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.

Parameters

NameTypeRequiredDescription
idstringnoTaxonomy category, e.g. “jurisdiction”, “chamber”, “formation”, “type”, “solution”, “publication”, “theme”. Omit to list the categories.
keystringnoA code within id to resolve to its label, e.g. id:“jurisdiction”, key:“cc” -> “Cour de cassation”. Requires id.
valuestringnoA label within id to resolve back to its code (the reverse of key). Requires id.
context_valuestringnoContext 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.

Example call

Arguments

{
  "id": "jurisdiction"
}

curl

curl -X POST https://gateway.pipeworx.io/fr-judilibre/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"fr_judilibre_taxonomy","arguments":{"id":"jurisdiction"}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('fr_judilibre_taxonomy', {
  "id": "jurisdiction"
});

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the fr-judilibre pack
{
  "mcpServers": {
    "fr-judilibre": {
      "url": "https://gateway.pipeworx.io/fr-judilibre/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 22, 2026