Skip to main content
Glama

update_account_item

DestructiveIdempotent

Sets the state of an existing case file (title, subtitle, case sheet), subfolder (name), saved reference (subfolder, set aside with a reason) or AI note (text, pinned, set aside). Only the fields given change; giving the same values again changes nothing. Overwrites the previous values. Notes written by the user cannot be changed. Nothing is deleted: deletion is delete_account_item. 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>",
      "id": "<id>"
    },
    "name": "update_account_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes"d_…", "c_…", "e_…" or "n_…", matching kind.
kindYescase_file (permission fiche), subfolder (ranger), item = saved reference (subfolder: ranger; set_aside: ecarter), note = AI note (text, pinned: notes_ia; set_aside: ecarter).
nameNosubfolder: new name.
textNonote: new text.
stageNocase_file: procedural stage.
titleNocase_file.
familyNocase_file: jud, adm, ce, eu or "".
numberNocase_file: case number.
pinnedNonote: true = follows its text into every case file holding it; false = back to one case file.
reasonNoitem, note: reason, with set_aside true; omit to reuse the earlier one.
partiesNocase_file: replaces the list; aliases only, never real names.
summaryNocase_file: summary.
subtitleNocase_file.
assistantNonote: assistant name stored with the new text.
deadlinesNocase_file: replaces the list; dates copied from the user.
set_asideNoitem, note: true = set aside (kept, not proposed again); false = restored.
case_file_idNonote, with pinned false: case file(s) it goes back to, one "d_…" or a list (a separate note in each; default: most recent holding the text; if no case file holds the text, unpinning is refused: it would delete the note; use delete_account_item).
jurisdictionNocase_file: court or authority.
subfolder_idNoitem: Subfolder "c_…"; "" = default "À ranger" area.
case_file_titleNoExact name of the case file, shown to the user for approval; must match its id, else nothing is done. subfolder/item/note: the one holding it.
subfolder_titleNoExact name of the subfolder ("À ranger" for ""), shown to the user; must match, else nothing is done. subfolder: current name; item: destination.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / case_file_id / description
      Previous value: -"note, with pinned false: case file(s) it goes back to, one \"d_…\" or a list (a separate note in each; default: most recent holding the text; if no case file holds the text, it becomes a plain note on the text)."New value: +"note, with pinned false: case file(s) it goes back to, one \"d_…\" or a list (a separate note in each; default: most recent holding the text; if no case file holds the text, unpinning is refused: it would delete the note; use delete_account_item)."
  2. Changed3 schema fields changed
    • addedInput schema / properties / case_file_id / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "items": {
      +      "type": "string"
      +    },
      +    "minItems": 1,
      +    "type": "array"
      +  }
      +]
    • changedInput schema / properties / case_file_id / description
      Previous value: -"note, with pinned false: case file it goes back to (default: most recent holding the text)."New value: +"note, with pinned false: case file(s) it goes back to, one \"d_…\" or a list (a separate note in each; default: most recent holding the text; if no case file holds the text, it becomes a plain note on the text)."
    • removedInput schema / properties / case_file_id / type
      Removed value: -"string"
  3. Changed2 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. subfolder/item/note: the one holding it.",
      +  "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. subfolder: current name; item: destination.",
      +  "type": "string"
      +}
  4. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it explains what 'destructive' actually means here – 'Overwrites the previous values' while nothing is deleted – and corroborates idempotency with 'giving the same values again changes nothing'. It adds non-obvious behavior: user-written notes are immutable, a title mismatch refuses the whole call, unpinning without a holding case file would delete the note and is refused, and write responses carry the case file's instructions labelled by author.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core write semantics and the deletion alternative are front-loaded, but the paragraph then repeats the phrase about active instructions 'each labelled with its author, returned as data' twice, and spends sentences on get_account_item's read behavior inside a write tool. Dense and useful overall, yet it could shed a sentence or two without losing information, especially since an output schema already exists.

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 21-parameter, four-mode tool with annotations and an output schema, the description covers the mode dispatch, partial-update semantics, immutability constraints, approval-matching refusals and auth requirements. The remaining details (per-parameter field meanings, return payload fields) are legitimately carried by the schema and output schema, so the gap is small.

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; the description goes further by stating the partial-update rule ('Only the fields given change'), that case_file_title/subfolder_title are user-approved exact copies whose mismatch aborts the call, and that parties carry aliases only, never real names. Some of this restates the schema's own 'must match its id, else nothing is done', so it is additive but not entirely new.

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 ('Sets the state of') and then enumerates the four distinct resources it operates on – case file, subfolder, saved reference, AI note – with the fields each accepts. It explicitly routes reads to get_account_item and deletions to delete_account_item, so an agent can separate it from siblings without opening the schema.

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

Usage Guidelines5/5

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

It states when to use alternatives concretely: 'Nothing is deleted: deletion is delete_account_item', reading is get_account_item with kind=case_file or kind=skill, and unpinning a note that no case file holds must instead go through delete_account_item. It also gives the preconditions (OAuth account required, title/subfolder_title must match) that determine whether a call will succeed.

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