Skip to main content
Glama

InProcess Cockpit

Supprimer un fichier

supprimer_fichier
Destructive

Supprime un fichier devenu inutile (dans les dossiers où l'écriture est permise).

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": {
      "cockpit": "<cockpit>",
      "chemin": "<chemin>"
    },
    "name": "supprimer_fichier"
  }
}

Input Schema

NameRequiredDescriptionDefault
cheminYes
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The one piece of added context, that deletion works only in writable folders, is useful, but the description never states that the deletion is permanent and irreversible, which is the single most important behavioral fact for 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?

A single front-loaded sentence with no filler. It is lean, though leanness here costs coverage rather than adding crispness.

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

Completeness2/5

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

This is a destructive, unannotated-beyond-hints mutation with no output schema and a half-documented schema. Missing are irreversibility, permission failure behavior, and path format, so an agent lacks what it needs to call it safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%: cockpit is documented in the schema, chemin is not. The description adds nothing about what chemin should look like (absolute vs relative, encoding) or about which cockpits qualify, so it fails to compensate for the uncovered parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ("Supprime un fichier"), so an agent can tell it apart from lire_fichier or ecrire_fichier. It stops short of distinguishing itself from mutation siblings like modifier_fichier or revenir_version.

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

Usage Guidelines2/5

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

"devenu inutile" gestures at a condition but gives no actionable when-to-use or when-not-to-use rule. Nothing tells the agent to prefer modifier_fichier or revenir_version when the content might still be needed, and no prerequisites are stated beyond the folder-permission parenthetical.

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