Skip to main content
Glama

Invite someone to the space by email

members_invite

Invite one person to this space by email. Sends the invitation email immediately.

POST /api/v1/members/invitations

For multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. Manage members only when the user asks. Requires the user to be an owner or admin of the space; a write-level key can grant the member role, and admin needs a manage-level key (a 403 says which). This sends an email immediately. Before calling it, list the exact email addresses and the role back to the user and get an explicit yes; never guess an address. Invite as admin only when the user explicitly asks. With no addresses, create an invite link instead and give the user its url to share.

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

Input Schema

NameRequiredDescriptionDefault
roleNomember
emailYes
targetSpaceIdNoBusabase space id. Call auth_verify first and ask the user which space to use when more than one is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only declare readOnly=false, openWorld=true, destructive=false. The description adds critical behavior beyond them: an email is dispatched immediately to a real person, permission thresholds vary by role, a 403 reveals which key level is needed, and multi-space accounts must resolve targetSpaceId via auth_verify.

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?

Front-loaded with purpose and side effect, then preconditions, then the confirmation protocol. Slightly penalized for repeating 'sends the invitation email immediately' twice and for the raw endpoint string, which adds little for an agent.

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 mutation tool with no output schema, the description covers side effects, permissions, confirmation protocol, and the invite-link alternative. It omits what is returned (e.g. invitation id) and duplicate/already-member handling, but nothing needed to call it safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, so the description must compensate, and it largely does: it constrains role=admin to explicit user request, forbids guessing email addresses, and explains targetSpaceId's multi-space resolution flow. It does not describe email format expectations or what happens on an already-invited address.

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 one person to this space by email') plus the immediate side effect, and implicitly differentiates from the sibling members_create_invite_link which it names as the fallback when no addresses exist.

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?

Explicit when-to-use ('Manage members only when the user asks'), when-not ('With no addresses, create an invite link instead'), preconditions (owner/admin, write-level vs manage-level key, 403 signal), and a required confirmation workflow before sending. Alternatives and exclusions are both named.

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.