Skip to main content
Glama

justicelibre

by io.github.Dahliyaal
OverviewDiscussionsAdmin

delete_account_item

Destructive

Permanently deletes one object of the user's JusticeLibre account: a case file (with all its content), a saved reference, a subfolder, a note, or an AI skill proposal not yet activated (skill, id s_… or p_…). No recycle bin. confirm=true states the user's explicit agreement; without it, nothing is deleted. Permission supprimer; a reference the AI saved itself can also be removed with permission notes_ia. To keep a trace with a reason instead: update_account_item with set_aside. Requires a JusticeLibre account (OAuth sign-in).

Example: delete_account_item(what="note", id="n_…", confirm=true)

Input Schema

NameRequiredDescriptionDefault
idYes"d_…", "e_…", "c_…", "n_…", or "s_…"/"p_…".
whatYes"folder", "element" (saved reference), "subfolder", "note" or "skill" (AI skill proposal not yet activated).
confirmNotrue = the user explicitly agreed; otherwise nothing is deleted.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / confirm / description
      Previous value: -"true = l'utilisateur a donné son accord ; sinon rien n'est supprimé."New value: +"true = the user explicitly agreed; otherwise nothing is deleted."
    • changedInput schema / properties / id / description
      Previous value: -"« d_… », « e_… », « c_… » ou « n_… »."New value: +"\"d_…\", \"e_…\", \"c_…\", \"n_…\", or \"s_…\"/\"p_…\"."
    • changedInput schema / properties / what / description
      Previous value: -"\"folder\", \"element\", \"subfolder\" ou \"note\"."New value: +"\"folder\", \"element\" (saved reference), \"subfolder\", \"note\" or \"skill\" (AI skill proposal not yet activated)."
  2. Added
  3. Removed
  4. Changed1 schema field changed
    • changedInput schema / properties / what / enum
      Previous value: -[
-  "folder",
-  "element",
-  "subfolder",
-  "note"
-]New value: +[
+  "folder",
+  "element",
+  "subfolder",
+  "note",
+  "skill"
+]
  5. Changed8 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "default": false,
+  "description": "true = l'utilisateur a donné son accord ; sinon rien n'est supprimé.",
+  "title": "Confirm",
+  "type": "boolean"
+}
    • removedInput schema / properties / confirmation
      Removed value: -{
-  "default": false,
-  "description": "Doit valoir true, après accord explicite de l'utilisateur ; sinon rien n'est supprimé.",
-  "title": "Confirmation",
-  "type": "boolean"
-}
    • changedInput schema / properties / id / description
      Previous value: -"Identifiant de l'objet (« d_… », « e_… », « c_… » ou « n_… »)."New value: +"« d_… », « e_… », « c_… » ou « n_… »."
    • removedInput schema / properties / quoi
      Removed value: -{
-  "description": "\"dossier\", \"element\", \"sous_dossier\" ou \"note\".",
-  "enum": [
-    "dossier",
-    "element",
-    "sous_dossier",
-    "note"
-  ],
-  "title": "Quoi",
-  "type": "string"
-}
    • addedInput schema / properties / what
      Added value: +{
+  "description": "\"folder\", \"element\", \"subfolder\" ou \"note\".",
+  "enum": [
+    "folder",
+    "element",
+    "subfolder",
+    "note"
+  ],
+  "title": "What",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "quoi",
-  "id"
-]New value: +[
+  "what",
+  "id"
+]
    • changedInput schema / title
      Previous value: -"compte_supprimer_objetArguments"New value: +"delete_account_itemArguments"
    • changedOutput schema / title
      Previous value: -"compte_supprimer_objetDictOutput"New value: +"delete_account_itemDictOutput"
  6. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes further: no recycle bin, the confirm gate meaning 'nothing is deleted without explicit user agreement', required permissions, and OAuth sign-in. These are exactly the behavioral traits beyond annotations an agent needs before calling a destructive 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?

Dense but front-loaded: the core action and types come first, then the confirm gate, then permissions, then the alternative, closing with a concrete example. The semicolon-chained permission clause is slightly cramped but every element earns its place.

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?

For a destructive mutation tool with an output schema already present, the description covers safety (confirm), authorization (permissions, OAuth), irreversibility (no recycle bin), and the escape hatch sibling. Nothing an agent needs to call it correctly is missing.

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% and the schema already documents the id prefixes, the what enum values, and the confirm default/semantics. The description largely restates this (id s_…/p_…, confirm meaning), adding little syntax or format detail beyond the schema, so the baseline 3 applies.

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 states a specific verb (permanently deletes) plus the resource and enumerates the exact item types (case file, saved reference, subfolder, note, unactivated skill). It also names the sibling update_account_item with set_aside as the non-destructive alternative, so an agent can distinguish it from siblings without opening schemas.

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 specifies when to use this tool (permanent deletion, no recycle bin), when not to (use update_account_item with set_aside to keep a trace with a reason), and the preconditions (confirm=true, permission supprimer, notes_ia for AI-saved references). All routing decisions are explicit.

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

All justicelibre toolsInspect
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.

Resources