Skip to main content
Glama

Coline

Invite someone

invite_member
Destructive

Invites a person to a team workspace by email, as a member or a guest; Coline emails them a link. Use it only when the person asks to invite someone, with the address they gave.

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

Input Schema

NameRequiredDescriptionDefault
roleNoGuests see only what's shared with them.member
emailYes
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".
targetPathNoInvited from a thing: its in-app path in this workspace, where they land after joining instead of Home.

Output Schema

NameRequiredDescriptionDefault
noteYes
emailedYes
inviteIdYes
expiresAtYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.6/5.0
Behavior3/5

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

The description adds the key external side effect beyond annotations: an email with a join link is sent to the invitee, which supports the openWorldHint=true declaration. However, it does not explain why destructiveHint=true (invites presumably grant access or can conflict with existing membership), nor what happens on a duplicate invitation despite idempotentHint=false, nor what permissions the inviter needs.

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 compact clauses, front-loaded with the action and side effect before the usage restriction. No filler, though the semi-colon-joined phrasing is slightly dense.

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?

An output schema exists, so return values need no explanation, and annotations cover the safety profile. Still, for a non-idempotent, destructive-flagged mutation, the description should say what happens when the address already has access or an invite is outstanding.

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 75%, so the baseline is 3. The description reinforces role ('as a member or a guest') and the email destination but adds nothing about the workspace slug format or the targetPath landing behavior, which remain documented only in the schema.

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 states a specific verb and resource ('Invites a person to a team workspace by email') and clarifies the two role outcomes ('as a member or a guest'). It does not name the closely related siblings (extend_invite, revoke_invite, add_team_member), so the boundary is clear by action but not explicitly contrasted.

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

Usage Guidelines4/5

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

It gives a real gating condition: 'Use it only when the person asks to invite someone, with the address they gave,' which rules out proactive or guessed-address invites. It stops short of naming alternatives such as extend_invite or add_team_member for related membership operations.

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