Skip to main content
Glama

InProcess Cockpit

Fonctionnement du cockpit

fonctionnement
Read-only

L'onglet « Fonctionnement » : ce que fait le cockpit, fonctionnalité par fonctionnalité.

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

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds nothing beyond that: it does not say what content is returned (text, markup, list of features), whether it is static documentation or user-specific, or how large the response is.

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 short sentence with the resource named first and no filler. It is efficient, though the brevity contributes to the vagueness noted elsewhere.

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?

The tool is simple (one required param, read-only), but with no output schema the description should indicate what an agent receives back and how it relates to the 'guide' sibling. Neither is addressed, so an agent cannot predict the return payload.

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?

Only one parameter exists and schema coverage is 100%, with the schema itself explaining it is the cockpit identifier from 'mes_cockpits'. The description adds no meaning on top, which is the expected baseline when the schema does the work.

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

Purpose3/5

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

The description names a resource ('l'onglet « Fonctionnement »') and outlines its content ('ce que fait le cockpit, fonctionnalité par fonctionnalité'), so an agent can guess this returns documentation about a cockpit's features. However, no retrieval verb is used and the phrasing largely restates the title 'Fonctionnement du cockpit', leaving the actual action implicit.

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?

There is no statement of when to call this versus related informational siblings such as 'guide' or 'mes_cockpits', and no prerequisites or exclusions. Usage is only inferable from the tab metaphor.

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