Skip to main content
Glama

InProcess Cockpit

Changer un membre

modifier_membre
Destructive

Change les rôles ou le nom d'un membre du cockpit en ligne, le désactive, le réactive, ou retire une invitation jamais ouverte.

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>",
      "action": "<action>"
    },
    "name": "modifier_membre"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomNo
emailYes
rolesNoPour action roles : la liste complète des rôles
actionYes
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?

Annotations already flag readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds a useful boundary: removal only applies to an invitation that was never opened, which tells the agent that an accepted member cannot be removed this way. It still says nothing about permissions required, whether deactivation is reversible (reactivation is listed, implying reversibility), or the response.

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 front-loaded sentence that packs the verb, the target resource, and the operation list with no filler. It is dense rather than sprawling, though the enumeration could be aligned more explicitly with the action enum values.

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 destructive mutation tool with no output schema and 5 parameters at 40% schema coverage, the definition is adequate but thin: one enum value ('renvoyer_invitation') has no description anywhere, and mutation consequences (what changes for the member, whether the change is immediate) are left implicit.

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 only 40%: 'cockpit' and 'roles' are documented in the schema, while 'email', 'nom' and 'action' are not. The description partially compensates by mapping nouns and verbs ('nom', 'désactive', 'réactive', 'retire') onto the action values, but it never explains that 'roles' requires the complete list nor what 'renvoyer_invitation' does, leaving meaningful gaps.

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 concrete verb ("Change") on a concrete resource ("un membre du cockpit en ligne") and enumerates the operations: role/name change, deactivate, reactivate, remove an unopened invitation. It is clearly distinguishable from the invitation-creating siblings, but it omits the 'renvoyer_invitation' action that the schema's enum exposes, so the stated purpose is incomplete.

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 when-to-use / when-not guidance and no reference to a sibling alternative such as the invitation tools. The agent must infer from the action list which situation selects this tool versus 'inviter_createur' or 'equipe_cockpit' when dealing with an outstanding invitation.

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