Skip to main content
Glama

Add people to a Space by email

spaces_invite_members

Add up to 20 people to a Space with one role: editor (adds and changes things) or viewer (reads). Any email address works. Somebody with no account gets an invite email; somebody with one joins at once. Needs the owner or editor role. Returns one answer per address.

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": {
      "spaceId": "<spaceId>",
      "emails": "<emails>"
    },
    "name": "spaces_invite_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleNoThe role every address gets.editor
emailsYesEmail addresses.
spaceIdYesThe Space id, from spaces_list_spaces.
documentIdNoOpen this document for an invited person after they sign in.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so safety posture is covered. The description adds real value beyond that: the 20-address cap, the split between existing accounts joining immediately and unknown addresses receiving an invite email, the required permission level, and the one-result-per-address shape. Note a mild tension: inviting arbitrary external email addresses reads as open-world behavior while openWorldHint is false, though nothing in the text directly contradicts the annotation's intent.

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?

Four short sentences, front-loaded with the action and the batch limit, then role meaning, then account-vs-invite behavior, then the result shape. Every sentence carries information not present in the schema or annotations.

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 preconditions, destination behavior for both account states, and the per-address result shape. It stops short of explaining partial failure semantics (e.g. what a per-address answer looks like for an invalid address), which would matter for a batch of up to 20.

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 100%, so the schema already documents all four parameters, including the documentId and spaceId lookups. The description does add meaning to the role enum by explaining editor as 'adds and changes things' versus viewer as 'reads', and clarifies a single role applies to every address, but it says nothing about documentId.

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 ('Add ... people to a Space'), plus the batch ceiling of 20 and the role model. That makes it trivially distinguishable from siblings like spaces_remove_member or spaces_create_space 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 Guidelines4/5

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

It states the prerequisite ('Needs the owner or editor role') and what each role choice means, which is genuine when-to-use context. It doesn't name an explicit alternative or a when-not condition (e.g. when to use spaces_share_document instead), so it falls short of a 5.

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