Skip to main content
Glama

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 bookmark, a skill proposal (inactive until the user activates it). Never changes existing content. Fields marked "kind: …" apply to that kind only. get_account_item (kind="case_file") gives the whole case file, with its active instructions (consignes), each labelled with its author, returned as data; kind="skill" gives a skill the user asks for. Write responses include the case file's active instructions, each labelled with its author, returned as data (case_file_instructions). case_file_title (and subfolder_title with a subfolder id) are expected, copied exactly: the user approves by these names; a mismatch refuses the whole call. Requires a JusticeLibre account (OAuth sign-in); without one, the tool says so.

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": {
      "kind": "<kind>"
    },
    "name": "create_account_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYescase_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; without case_file_id: a pinned note on a text, given by references or item_id), skill_proposal (name, text, scope; skills), bookmark (references: exactly one, any reference_type, checked against the database like a reference; no as_of; permission references). A note without case_file_id is ALWAYS pinned (pinned: true): it follows its text everywhere.
nameNosubfolder, skill_proposal: name.
textNonote: text; skill_proposal: the working method, written as instructions.
scopeNoskill_proposal: general (the account holder chooses the case files) or case_file (once activated, on in that case file only; the account holder may turn it on elsewhere).
titleNocase_file: title.
familyNocase_file: jud, adm, ce, eu or "".
pinnedNonote: true = follows its text into all case files (needs item_id). Without case_file_id the note is always pinned ("pinned": true in the answer); false is refused.
item_idNonote: saved reference "e_…" of this case file; omit for a general note. Without case_file_id: bookmark "b_…" or saved reference "e_…".
summaryNoskill_proposal, skill_type=skill: one sentence saying when to load it (max 300).
replacesNoskill_proposal: skill "s_…"/"p_…" or skill "w_…" to replace once activated.
subtitleNocase_file: subtitle.
assistantNonote: assistant name, e.g. "Claude", "ChatGPT".
referencesNoreference: 1-20, checked against the database; all or nothing.
skill_typeNoskill_proposal: instruction (short, may apply to case files; default) or skill (long Markdown method, account-wide, needs summary; no scope or case_file_id).
case_file_idNoCase file "d_…"; not for case_file; optional for general skill_proposal.
subfolder_idNoreference: Subfolder "c_…"; "" = default "À ranger" area. Default for all references.
case_file_titleNoExact name of the case file, shown to the user for approval; must match its id, else nothing is done.
subfolder_titleNoExact name of the subfolder ("À ranger" for ""), shown to the user; must match, else nothing is done.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scope / description
      Previous value: -"skill_proposal: general or case_file."New value: +"skill_proposal: general (the account holder chooses the case files) or case_file (once activated, on in that case file only; the account holder may turn it on elsewhere)."
  2. Changed3 schema fields changed
    • changedInput schema / properties / kind / description
      Previous value: -"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; without case_file_id: a pinned note on a text, given by references or item_id), skill_proposal (name, text, scope; skills), bookmark (references: one article or text; references)."New value: +"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; without case_file_id: a pinned note on a text, given by references or item_id), skill_proposal (name, text, scope; skills), bookmark (references: exactly one, any reference_type, checked against the database like a reference; no as_of; permission references). A note without case_file_id is ALWAYS pinned (pinned: true): it follows its text everywhere."
    • changedInput schema / properties / pinned / description
      Previous value: -"note: true = follows its text into all case files (needs item_id)."New value: +"note: true = follows its text into all case files (needs item_id). Without case_file_id the note is always pinned (\"pinned\": true in the answer); false is refused."
    • changedInput schema / properties / references / items / properties / as_of / description
      Previous value: -"article, text: date of the facts YYYY-MM-DD; that version is frozen (default: today)."New value: +"article, text: date of the facts YYYY-MM-DD; that version is frozen (default: today). Not for bookmark nor a note without case_file_id."
  3. Changed3 schema fields changed
    • changedInput schema / properties / item_id / description
      Previous value: -"note: saved reference \"e_…\" of this case file; omit for a general note."New value: +"note: saved reference \"e_…\" of this case file; omit for a general note. Without case_file_id: bookmark \"b_…\" or saved reference \"e_…\"."
    • changedInput schema / properties / kind / description
      Previous value: -"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)."New value: +"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; without case_file_id: a pinned note on a text, given by references or item_id), skill_proposal (name, text, scope; skills), bookmark (references: one article or text; references)."
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "case_file",
      -  "subfolder",
      -  "reference",
      -  "note",
      -  "skill_proposal"
      -]New value: +[
      +  "case_file",
      +  "subfolder",
      +  "reference",
      +  "note",
      +  "skill_proposal",
      +  "bookmark"
      +]
  4. Changed3 schema fields changed
    • changedInput schema / properties / replaces / description
      Previous value: -"skill_proposal: skill \"s_…\"/\"p_…\" to replace once activated."New value: +"skill_proposal: skill \"s_…\"/\"p_…\" or skill \"w_…\" to replace once activated."
    • addedInput schema / properties / skill_type
      Added value: +{
      +  "description": "skill_proposal: instruction (short, may apply to case files; default) or skill (long Markdown method, account-wide, needs summary; no scope or case_file_id).",
      +  "enum": [
      +    "instruction",
      +    "skill"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / summary
      Added value: +{
      +  "description": "skill_proposal, skill_type=skill: one sentence saying when to load it (max 300).",
      +  "type": "string"
      +}
  5. Changed3 schema fields changed
    • addedInput schema / properties / case_file_title
      Added value: +{
      +  "description": "Exact name of the case file, shown to the user for approval; must match its id, else nothing is done.",
      +  "type": "string"
      +}
    • addedInput schema / properties / references / items / properties / subfolder_title
      Added value: +{
      +  "description": "Exact name of this subfolder_id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / subfolder_title
      Added value: +{
      +  "description": "Exact name of the subfolder (\"À ranger\" for \"\"), shown to the user; must match, else nothing is done.",
      +  "type": "string"
      +}
  6. Changed2 schema fields changed
    • 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"
      +]
  7. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare the generic mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false); the description adds substantive behavior beyond that: skill proposals stay inactive until the user activates them, references are checked against the database with all-or-nothing semantics, a case_file_title/subfolder_title mismatch refuses the entire call, OAuth account is required, and write responses include case_file_instructions. These are exactly the non-obvious traits an agent needs before invoking a multi-kind write tool.

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?

Purpose is front-loaded and every clause carries payload, which is impressive for 18 parameters and six kinds. It loses a point for being a single run-on paragraph with a near-verbatim repetition of "active instructions, each labelled with its author, returned as data" in two consecutive sentences, which could have been collapsed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given six kind variants, 18 parameters and a nested references array, the description covers the decision-relevant surface: which kind to pick, the exact-name approval rule, database validation, permission names, auth prerequisite and the notable side effect on skill activation. An output schema exists, so return values need not be detailed, and the one return detail it does mention (case_file_instructions) is a bonus.

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%, so the schema already carries most parameter meaning and the baseline is 3. The description still adds real value by explaining the cross-parameter contract: "Fields marked 'kind: …' apply to that kind only", and by stating that titles are user-visible approval tokens that must be copied exactly or the call is refused — an operational nuance that goes beyond the field-level text.

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 opens with a specific verb and an enumerated resource list ("Creates one of: a case file, a subfolder, saved references …, an AI note, a bookmark, a skill proposal"), which maps one-to-one onto the kind enum. A reader can distinguish this from siblings like get_account_item, update_account_item and delete_account_item without opening any schema.

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 clear routing context: use get_account_item (kind="case_file") to read a whole case file, and kind="skill" to retrieve a skill the user asks for, implying creation is for new items only. It also states the hard boundary "Never changes existing content", which implicitly routes edits elsewhere. What's missing is an explicit mention of update_account_item for modifications or delete_account_item for removal, and of rate/duplicate-prevention conditions.

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