Skip to main content
Glama

InProcess Cockpit

Inviter dans l'équipe du cockpit

inviter_equipe

Invite une personne à utiliser le cockpit avec ses rôles (les rôles du cockpit : equipe_cockpit). En ligne, elle reçoit son invitation tout de suite ; sinon, elle la recevra à 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>",
      "email": "<email>",
      "roles": "<roles>"
    },
    "name": "inviter_equipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomNo
emailYes
rolesYesIdentifiants des rôles, ex. ["technicien"]
cockpitYesIdentifiant du cockpit (mes_cockpits)

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false and destructiveHint=false, so the description need not repeat write behavior. It adds useful timing context: an online invitee receives the invitation immediately, otherwise at first mise en ligne. It still omits handling for duplicate/already-member cases and permission requirements.

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?

Two front-loaded sentences communicate the action and the delivery caveat without redundant wording. The parenthetical role-source note is compact and relevant.

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?

For a non-destructive invite mutation, the description covers the action, role source, and invitation delivery timing. It still leaves out edge cases such as duplicate invites, permission requirements, and guidance for the optional nom parameter.

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?

The schema documents cockpit and roles, and the description adds that role identifiers come from equipe_cockpit. However, email and optional nom are not explained in the description, leaving part of the 50% schema coverage gap unaddressed.

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: inviting a person to use the cockpit with roles, and points to equipe_cockpit as the role source. It is clear on its own, but does not explicitly distinguish itself from siblings such as inviter_createur or modifier_membre.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied as adding a person to the cockpit team with existing cockpit roles. There is no explicit when-to-use guidance versus alternatives or prerequisites for inviting someone.

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