Skip to main content
Glama

Invite a workspace member

invite_workspace_member
Idempotent

Sends an email invitation to join an authorized workspace as Member or Admin. The recipient’s acceptance is required before membership becomes active.

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_id": "<workspace_id>",
      "email": "<email>",
      "role": "<role>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "invite_workspace_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
emailYes
workspace_idYesExact workspace ID from list_workspaces. Never infer a workspace from a project name.
idempotency_keyYesUnique write key. Reuse the same key and input after an uncertain response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly=false, openWorld=true, idempotent=true and destructive=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: an external email is dispatched and membership stays pending until the recipient accepts, which tells the agent the call's effect is deferred rather than immediate. It omits permission requirements and what the response contains.

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?

Two short sentences with zero filler, front-loading the action and following with the one detail an agent must know (acceptance required before activation). Nothing is repeated from the title 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?

With no output schema, the description would ideally state what comes back (for example an invitation ID or pending status), and it does not. Everything else an agent needs to call this correctly — the action, the pending-acceptance model, the role values — is either present or already carried by the rich annotations and schema.

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%, but the two undescribed parameters (role, email) are self-evident from an enum and an email format, while workspace_id and idempotency_key carry their own schema descriptions. The description only reinforces the role values ('Member or Admin') and adds nothing about idempotency semantics or workspace_id sourcing, so it is baseline rather than compensating.

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 names a specific verb and resource ('Sends an email invitation to join an authorized workspace as Member or Admin') and adds the two-phase nature of membership, which separates it from accept_workspace_invitation. It stops short of explicitly naming update_workspace_member or accept_workspace_invitation as alternatives, so the differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

Usage is implied by 'authorized workspace' — the agent can gather this is for adding a not-yet-member by email to a workspace it already controls. There are no explicit when-to-use or when-not conditions, no mention of prerequisites such as caller admin rights, and no routing to accept_workspace_invitation or update_workspace_member for the follow-up cases.

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