Skip to main content
Glama

InProcess Cockpit

Équipe du cockpit

equipe_cockpit
Read-only

Les membres du cockpit et leurs rôles. En ligne : la vraie équipe. Pas encore en ligne : les comptes d'essai de l'aperçu, et les invitations prévues pour la première mise en ligne.

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

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.6/5.0
Behavior4/5

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

With readOnlyHint=true already declaring the safe-read profile, the description adds genuinely non-obvious behavioural context: the returned set mixes the live team with preview trial accounts and invitations scheduled for first go-live. That interpretation rule is exactly the kind of nuance annotations cannot convey. It stops short of describing ordering, counts, or response shape.

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

Conciseness5/5

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

Three short sentences, front-loaded with what the tool returns, then the online/not-yet-online distinction. No filler and no repetition of the title.

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 listing tool with annotations covering safety and no output schema, the description covers what comes back and how to interpret the mixed membership. Minor gaps remain: it does not mention the role values or whether the caller must be a member of the cockpit.

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 coverage is 100% and the single 'cockpit' parameter is documented in the schema as an identifier from mes_cockpits. The description adds no meaning about that parameter, so the baseline of 3 for a fully documented schema 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 precisely ('Les membres du cockpit et leurs rôles') and defines the scope of who is counted, which lets an agent distinguish this from a general organization roster. It lacks an explicit verb such as 'list' or 'return' and never names the neighbouring tools it differs from, so the purpose is clear but not maximally sharp.

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 tool, when not to, or which sibling to prefer (e.g. equipe_organisation, demandes_equipe, inviter_equipe). The usage is only inferable from the noun phrase describing the content, with no conditions or exclusions given.

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