boondmanager-mcp-server

Supprimer un(e) candidat

boond_candidates_delete

Destructive

Permanently delete a candidate record from BoondManager by ID. Use only after verifying the ID with boond_candidates_get; prefer boond_candidates_update to deactivate instead of destroy.

Instructions

Supprime définitivement un(e) candidat de BoondManager.

Quand : uniquement sur demande explicite de l'utilisateur, et après avoir vérifié l'ID avec boond_candidates_get. Plutôt que : boond_candidates_update pour désactiver ou changer l'état d'un enregistrement sans le détruire — c'est presque toujours l'intention réelle.

⚠️ Irréversible, sans corbeille côté API.
Si le client MCP annonce la capacité elicitation, une confirmation est demandée à l'utilisateur final et un refus annule l'appel (structuredContent.deleted: false + reason) ; sinon la suppression part directement.

Returns : { id, deleted, reason? } — vérifier deleted, qui vaut false en cas de refus utilisateur.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Identifiant unique de l'entité BoondManager (numérique)

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`reason`	No	Présent quand la suppression n'a pas eu lieu (ex: refus utilisateur)
`deleted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.12.2Aug 14, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed4 schema fields changedv2.7.0Jun 19, 2026

changedInput schema / properties / id / description

Previous value: -"Identifiant unique de l'entité BoondManager"New value: +"Identifiant unique de l'entité BoondManager (numérique)"

removedInput schema / properties / id / minLength
```
Removed value: -1
```
addedInput schema / properties / id / pattern
```
Added value: +"^\\d+$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "deleted": {
+      "type": "boolean"
+    },
+    "id": {
+      "type": "string"
+    },
+    "reason": {
+      "description": "Présent quand la suppression n'a pas eu lieu (ex: refus utilisateur)",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "deleted"
+  ],
+  "type": "object"
+}

First observedv2.1.0May 30, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already include destructiveHint=true, but the description goes beyond them by warning that deletion is irreversible, has no trash/recycle bin on the API side, and can be bypassed or canceled depending on the MCP client's 'elicitation' capability. It also explains refusal behavior via 'structuredContent.deleted: false' and 'reason'. These are significant behavioral details the annotations do not convey.

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

Conciseness5/5

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

The description is front-loaded with the main delete action, followed by compact 'Quand' and 'Plutôt que' lines. The important warnings and return behavior are placed in short bullet phrases. Every sentence contributes distinct operational value, and there is no fluff or tautological text.

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, single-parameter tool, the description covers all key context: when deletion is appropriate, which sibling to use instead, the irreversibility risk, the possible user confirmation flow, and the output combination for a refusal. Nothing relevant for an agent to invoke this tool 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?

There is only one parameter, 'id', and the input schema already describes it as the unique numeric BoondManager entity ID with a regex pattern. Since schema coverage is 100%, the baseline is 3; the description adds no extra parameter details beyond the advice to verify the ID first, which is more operational guidance than parameter semantic. This does not substantially raise the score.

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 the exact action with a specific verb and resource: 'Supprime définitivement un(e) candidat de BoondManager.' It also distinguishes the tool from siblings by explicitly pointing to boond_candidates_update for non-destructive state changes and boond_candidates_get for verifying the ID, so an agent can clearly recognize this tool's unique destructive purpose.

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?

The description gives explicit 'Quand' guidance: only on explicit user request and after verifying the ID with boond_candidates_get. It also tells the agent to prefer boond_candidates_update when the real intention is to disable or change state without destroying, making both when to use and when not to use this delete tool unambiguous.

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

Deploy Server