Skip to main content
Glama

InProcess Cockpit

Lire un fichier

lire_fichier
Read-only

Lit un fichier du cockpit. Le code du noyau (node_modules/@coulisse) n'est pas lisible ; ses signatures sont décrites dans le skill coulisse-kernel-api.

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": "lire_fichier"
  }
}

Input Schema

NameRequiredDescriptionDefault
cheminYesChemin depuis la racine du cockpit
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds one genuinely useful behavioral constraint — the kernel directory is blocked and must be reached through a skill — but says nothing about missing-file behavior, path traversal limits, or file size/encoding constraints.

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. The core action comes first and the restriction-plus-workaround follows, which is exactly the right ordering for an agent scanning the definition.

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?

This is a simple two-parameter read tool with a full schema, readOnlyHint, and no output schema, so the description need not explain return values. The one gotcha an agent would otherwise hit — the unreadable kernel directory — is disclosed. Minor gap: no mention of what happens on a nonexistent path.

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 description coverage is 100%, with both 'chemin' (path from cockpit root) and 'cockpit' (cockpit identifier) documented in the schema itself. The description adds no further meaning about path syntax, relative vs absolute handling, or cockpit ID format, so it merits only the baseline 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?

States a specific verb ("Lit") and a specific resource ("un fichier du cockpit"), plus the scope boundary that the file must live under the cockpit root. This is enough to distinguish it from ecrire_fichier, modifier_fichier, and supprimer_fichier without inspecting any schema.

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

Usage Guidelines4/5

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

The description names an explicit exclusion (kernel code under node_modules/@coulisse is not readable) and routes the agent to the alternative (skill coulisse-kernel-api for signatures). It does not give a positive trigger for when to prefer this tool over lire_skill or fichiers, but the negative case is stated clearly.

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