Skip to main content
Glama

InProcess Cockpit

Modifier un fichier

modifier_fichier

Remplace un passage exact d'un fichier par un autre. Le passage doit être unique, sauf si tout_remplacer.

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>",
      "ancien": "<ancien>",
      "nouveau": "<nouveau>"
    },
    "name": "modifier_fichier"
  }
}

Input Schema

NameRequiredDescriptionDefault
ancienYesLe texte exact à remplacer
cheminYes
cockpitYesIdentifiant du cockpit (mes_cockpits)
nouveauYesLe texte qui le remplace
tout_remplacerNo

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description is consistent with a mutating operation, so there is no contradiction. It adds real behavioral context by disclosing the uniqueness failure condition, but omits what happens on failure, whether the change is reversible (relevant given the revenir_version sibling), and whether a backup or version is created.

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?

Two short sentences with no filler: the core action first, then the constraint that governs its failure. Every clause earns its place and the critical constraint is not buried.

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 5-parameter file-mutation tool with no output schema, the description covers the action and the main failure mode, and annotations cover the safety profile. The remaining gap is the undocumented chemin parameter and post-mutation behavior, which are modest relative to the tool's simplicity.

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 60%, with ancien, nouveau and cockpit documented in-schema. The description adds genuine meaning for tout_remplacer, which the schema leaves entirely undocumented, but chemin and the exact matching semantics (case, whitespace, partial-line) are never clarified in either place.

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?

The description gives a specific verb (remplace) and resource (un passage exact d'un fichier), so it is clearly a targeted text-substitution tool rather than a whole-file writer. It does not name or contrast itself with ecrire_fichier or supprimer_fichier, so an agent must infer the distinction from the verb alone.

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

Usage Guidelines3/5

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

It states a usage condition — the passage must be unique unless tout_remplacer is set — which implicitly tells the agent when to use the override flag. It says nothing about when to choose this over ecrire_fichier, or what the prerequisite is (file must exist, readable, correct cockpit), leaving the main routing decision to inference.

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