Skip to main content
Glama

InProcess Cockpit

Le cockpit en ligne

etat_en_ligne
Read-only

Si le cockpit est en ligne pour l'équipe, à quelle adresse, s'il y a des changements à publier, une publication en cours ou refusée.

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

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.5/5.0
Behavior4/5

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

With readOnlyHint=true already declaring safety, the description adds genuine value by disclosing the shape of the answer: address, pending changes, and the in-progress/refused publication states. Since no output schema exists, this enumeration is the only signal an agent has about what comes back, though it does not say how those states are represented.

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?

One sentence with no redundant wording, and the primary subject (is the cockpit online) is front-loaded. The structure is a run-on chain of indirect clauses that takes a pass to parse, but nothing could be cut without losing reported facets.

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 one-parameter read-only status tool with no output schema, the description covers the relevant returned facets well enough to call it correctly. The main residual gap is usage framing relative to sibling publication tools, not the mechanics of the call.

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?

There is a single parameter whose schema description ('Identifiant du cockpit (mes_cockpits)') is fully covered at 100%, so the baseline applies. The description adds nothing about the cockpit identifier or where to obtain it, but the schema already carries that meaning.

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?

The description specifies the resource (the cockpit's online state) and enumerates the facets reported: online-for-team status, address, pending changes, and publication in progress or refused. It is clearly more than a restatement of the name, but it never distinguishes itself from siblings such as 'avant_publication' or 'publier', which plausibly overlap with the publication-status facet.

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 explicit when-to-use statement, no prerequisite, and no named alternative for the overlapping publication concerns. The agent must infer that this is the read-only status check to call before or instead of 'publier'.

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