Skip to main content
Glama

InProcess Cockpit

Inviter un créateur

inviter_createur

Invite quelqu'un dans l'organisation pour construire les cockpits avec la personne (il reçoit un email). Réservé aux propriétaires de l'organisation. L'équipe qui utilise un cockpit s'invite avec inviter_equipe.

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": {
      "email": "<email>"
    },
    "name": "inviter_createur"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNocreateur par défaut
emailYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds the meaningful behavior beyond that — the invitee receives an email and the caller must be an organisation owner. It does not cover duplicate-invite handling, whether the invite expires, or whether the role can be changed afterwards.

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 sentences, each earning its place: capability plus side effect first, permission constraint second, sibling redirect last. No filler or restatement 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 two-parameter mutation with no output schema and minimal annotations, the description supplies the side effect, the authorization gate, and the sibling alternative. Remaining gaps (response shape, idempotency on repeat invites) are modest for an invitation tool.

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 50%: role documents itself as "createur par défaut", but email carries no schema description. The description implies email is the address that receives the invitation and frames the invitee as a cockpit builder, which partially compensates, but it never explains when to pass role=proprietaire instead of the default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: invite a person into the organisation so they can build cockpits. The final sentence explicitly positions it against the sibling inviter_equipe, so an agent can route between the two without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite ("Réservé aux propriétaires de l'organisation") and an explicit alternative with its selection condition (use inviter_equipe for a team that operates a cockpit). Nothing about when to pick this tool is left to inference.

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