justicelibre

create_account_item

Creates one of: a case file, a subfolder, saved references (articles, statutes, decisions, CADA opinions, CNIL deliberations, doctrine), an AI note, a skill proposal (inactive until the user activates it). Never changes existing content. Fields marked "kind: …" apply to that kind only. Requires a JusticeLibre account (OAuth sign-in); without one, the tool says so.

Input Schema

Name	Required	Description
`kind`	Yes	case_file (requires title; permission creer_dossiers), subfolder (case_file_id, name; ranger), reference (case_file_id, references; references), note (case_file_id, text, assistant; notes_ia), skill_proposal (name, text, scope; skills).
`name`	No	subfolder, skill_proposal: name.
`text`	No	note: text; skill_proposal: the working method, written as instructions.
`scope`	No	skill_proposal: general or case_file.
`title`	No	case_file: title.
`family`	No	case_file: jud, adm, ce, eu or "".
`pinned`	No	note: true = follows its text into all case files (needs item_id).
`item_id`	No	note: saved reference "e_…" of this case file; omit for a general note.
`replaces`	No	skill_proposal: skill "s_…"/"p_…" to replace once activated.
`subtitle`	No	case_file: subtitle.
`assistant`	No	note: assistant name, e.g. "Claude", "ChatGPT".
`references`	No	reference: 1-20, checked against the database; all or nothing.
`case_file_id`	No	Case file "d_…"; not for case_file; optional for general skill_proposal.
`subfolder_id`	No	reference: Subfolder "c_…"; "" = default "À ranger" area. Default for all references.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 18, 2026

changedInput schema / properties / references / items / properties / source / description

Previous value: -"decision: dila (judicial), admin (TA/CAA), ariane (CE), cedh, cjue, kali."New value: +"decision: dila (judicial), admin (TA/CAA), ariane (CE)…"

changedInput schema / properties / references / items / properties / source / enum

Previous value: -[
-  "dila",
-  "admin",
-  "ariane",
-  "cedh",
-  "cjue",
-  "kali"
-]New value: +[
+  "dila",
+  "admin",
+  "ariane",
+  "cedh",
+  "cjue",
+  "kali",
+  "travaux"
+]

AddedOct 15, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the write profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds value beyond them: 'Never changes existing content' refines the non-destructive claim, and 'skill proposal (inactive until the user activates it)' discloses a non-obvious lifecycle quirk. It doesn't discuss validation behavior or the all-or-nothing reference creation here.

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?

Front-loaded with the enumerated outcomes and kept to a few tight sentences. The long parenthetical list of reference kinds is slightly dense but earns its place by clarifying scope. No filler sentences.

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 14-parameter polymorphic write tool with an output schema, the description covers the account prerequisite, non-mutating guarantee, per-kind field convention, and skill-proposal lifecycle. Return values are handled by the output schema, so little is missing, though per-kind side effects could be richer.

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 coverage is 100%, so the baseline is 3, but the description adds a genuinely useful meta-rule: 'Fields marked "kind: …" apply to that kind only', which explains how to read the 14-parameter polymorphic schema. That helps an agent understand the kind-dependent parameters that the schema alone only hints at.

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 ('Creates') and enumerates exactly what can be created (case file, subfolder, references, AI note, skill proposal), which is essential for a polymorphic tool. This clearly separates it from siblings like update_account_item, delete_account_item and get_account_item.

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?

Gives a prerequisite ('Requires a JusticeLibre account (OAuth sign-in); without one, the tool says so') and an important scoping rule ('Never changes existing content'), which implicitly routes modifications to update_account_item. It stops short of naming an explicit alternative tool, so 4 rather than 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All justicelibre tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.