Skip to main content
Glama

Team: Invite member

team_invite_member
Destructive

Invite a colleague to the user's Team workspace by email. Each member gets a separate login, isolated provider Scope and their own connected accounts; the team only centralizes billing and seats. Only team owners/admins can invite. When no seat is free, the result explains how to add a paid seat (team_add_seats). If the user is not on Team, propose account_change_plan(plan='team').

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

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address of the person to invite.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations declare destructiveHint=true, idempotentHint=false and openWorldHint=true, but the description adds real context beyond them: the invited member gets a separate login and isolated provider scope, seats are the constrained resource, and the failure path returns remediation guidance. It stops short of saying what a successful invite returns (pending state, expiry, email delivery) or how to revoke it, which matters for a destructive mutation.

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?

The description is four sentences, front-loaded with the action and tightened by the immediate permission and failure-path guidance. The mid-section explaining the team model ('isolated provider Scope') is useful but slightly jargon-heavy, keeping it just below fully economical.

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?

With no output schema, the description does address what happens on the seat-exhausted path, which is the main failure an agent would hit. It leaves the successful return (invite pending vs. accepted, email sent) unstated for a destructive, non-idempotent mutation, which is a modest remaining gap.

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?

There is only one parameter and schema description coverage is 100%, with the email format and pattern fully specified in the schema. The description's 'by email' phrasing adds no constraint or meaning beyond that, so this sits at the baseline for a fully-documented single-parameter tool.

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?

The first sentence names a specific verb and resource ('Invite a colleague to the user's Team workspace by email'), and the second sentence clarifies the team model so the agent understands this is a workspace-seat addition, not a shared-account grant. It is readily distinguishable from siblings such as team_add_seats and account_change_plan.

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?

The description states the authorization precondition (only team owners/admins can invite), names the fallback when no seat is free (team_add_seats), and routes non-Team users to account_change_plan(plan='team'). That is explicit when-to-use, when-not, and named alternatives in one place.

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.