Skip to main content
Glama

InProcess Cockpit

Vue d'ensemble du cockpit

vue_ensemble
Read-only

Le cockpit d'un coup d'œil : espaces, pages publiques, en ligne ou non, équipe, demandes, chiffres, changements du mois.

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

Input Schema

NameRequiredDescriptionDefault
cockpitYesIdentifiant du cockpit (mes_cockpits)

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, so the description's burden is lighter. It adds useful scope context — that the result spans multiple domains including online/offline status and changes over the current month — but says nothing about result size, permissions required, or whether missing sections are omitted.

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 short front-loaded sentence with a colon-separated content list — no filler and the summary intent comes first. The list is dense but each item conveys a distinct returned section.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, enumerating the covered sections is the main way to describe the return value, and the description does that. However, for a multi-domain aggregate tool it omits how the data is structured and whether the caller should fall back to specific sibling tools for detail, leaving a gap.

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 the single 'cockpit' parameter is documented as an identifier from mes_cockpits, so the schema does the work. The description never mentions the parameter at all, adding no meaning beyond it; 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?

The description names the resource (the cockpit) and enumerates what the overview covers: spaces, public pages, online status, team, requests, figures, monthly changes. That makes the aggregating/summary nature clear enough to distinguish it from focused siblings like equipe_cockpit or etat_en_ligne. It lacks an explicit verb ('returns', 'summarizes'), so it falls short of a full 5.

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 instead of the narrower sibling tools, no prerequisite (e.g. needing a cockpit id from mes_cockpits), and no exclusions. The 'd'un coup d'œil' phrasing only weakly implies 'use this for a first look at everything', leaving the agent to infer the routing decision.

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