Skip to main content
Glama

InProcess Cockpit

Lire un skill

lire_skill
Read-only

Lit un skill de construction (SKILL.md, ou un autre de ses fichiers) et liste ses fichiers.

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": {
      "nom": "<nom>"
    },
    "name": "lire_skill"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomYesNom du skill, ex. coulisse-screens
fichierNoFichier du skill (SKILL.md par défaut), ex. charte.html

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely new behavioral context beyond the annotation: the response includes a listing of the skill's files, not just the requested document's contents. It says nothing about what happens when the skill or requested file does not exist.

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; the verb and resource come first, followed by the file-listing side effect. The trailing clause is slightly compressed but nothing is wasted.

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 two-parameter read-only tool with no output schema, the description covers the resource, the selectable file, and the extra file listing. Only error behavior and the boundary with the generic file-reading siblings remain unaddressed.

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% and both parameters are documented there, including 'SKILL.md par défaut' and the example values. The description restates the default file rather than adding format or resolution rules, so the baseline 3 applies.

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 — reads a construction skill (SKILL.md or one of its files) — and adds that it also lists the skill's files, which is more specific than the title alone. It does not explicitly distinguish itself from the sibling lire_fichier, so an agent must infer that a 'skill' is a bundle rather than a plain file.

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?

The description gives no when-to-use or when-not guidance, and never mentions siblings such as lire_fichier or fichiers that could read the underlying file instead. The default-file behavior is stated, but that is parameter semantics rather than routing guidance.

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