Skip to main content
Glama

InProcess Cockpit

Écrire un fichier

ecrire_fichier

Écrit un fichier entier (créé s'il n'existe pas). Permis : src/, migrations/, tests/, AGENTS.md, FONCTIONNEMENT.md, coulisse.config.ts.

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>",
      "contenu": "<contenu>"
    },
    "name": "ecrire_fichier"
  }
}

Input Schema

NameRequiredDescriptionDefault
cheminYesChemin depuis la racine du cockpit
cockpitYesIdentifiant du cockpit (mes_cockpits)
contenuYesLe contenu complet du fichier

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/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; the description adds that a missing file is created and which paths are writable, which is genuine extra context. It does not disclose what happens to an existing file's content (full overwrite vs. error), what occurs when the path is outside the whitelist, or encoding behavior — meaningful gaps for a whole-file write.

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, no filler, with the operation and its create-if-missing behavior front-loaded before the path constraint. Every clause carries information an agent needs.

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 low-complexity, 3-parameter write tool with annotations covering the safety profile and a fully documented schema, the description covers the essentials: full-file write, creation, and path whitelist. Only the overwrite semantics of an existing file remain unstated.

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 would be 3. The whitelist nonetheless adds real meaning for the 'chemin' parameter by constraining which values are legal, going beyond what the schema states.

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?

States a specific verb and resource ('Écrit un fichier entier') and the 'entier' qualifier implicitly separates it from modifier_fichier's partial edits. It does not explicitly name a sibling, so differentiation is left partly to inference.

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?

The permitted-path list ('src/, migrations/, tests/, AGENTS.md, ...') is a strong constraint on when the tool may be used, and 'créé s'il n'existe pas' covers the create case. However there is no explicit routing guidance telling the agent to prefer modifier_fichier for edits or lire_fichier first, so the when-to-use-vs-alternative decision is only implied.

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