Skip to main content
Glama

InProcess Cockpit

Fichiers du cockpit

fichiers
Read-only

Les fichiers du cockpit tels qu'ils sont maintenant (écrits mais pas encore vérifiés compris).

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

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)
dossierNoUn dossier, ex. src/modules

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.4/5.0
Behavior3/5

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

readOnlyHint=true already declares the safe-read profile, so the description's only added value is the note that unverified/draft files are included in the result set — genuinely useful scope information. It says nothing about ordering, pagination, size limits, or what a returned file entry looks like, so the extra context is thin.

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

Conciseness3/5

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

A single short sentence with no padding, so nothing is wasted, but the brevity comes at the cost of substance rather than from tight editing. The parenthetical is clipped and slightly cryptic in phrasing.

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?

For a two-parameter read tool with no output schema, the description should at minimum say that it returns a list of the cockpit's files (paths vs. contents) and how dossier narrows the result. Neither is covered, and no sibling routing is offered, leaving real gaps for correct invocation.

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% (both cockpit and dossier are documented inline, including an example path), so the schema carries parameter meaning. The description adds nothing beyond the schema — no note on whether dossier is a filter or a prefix, or whether omitting it returns everything. Baseline 3 applies.

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

Purpose2/5

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

The description essentially restates the tool title ("Fichiers du cockpit") as a noun phrase with no verb saying what it does — list, return paths, return contents? The parenthetical "écrits mais pas encore vérifiés compris" does add a scope hint (drafts included), which saves it from being a pure tautology, but an agent still cannot tell precisely what operation this performs.

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?

No when-to-use guidance and no mention of the obvious alternatives in the sibling set (lire_fichier, ecrire_fichier, modifier_fichier, supprimer_fichier, avant_publication). The listing intent is only implied by the noun "fichiers"; nothing states when an agent should call this instead of reading a single file.

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