Skip to main content
Glama

Invite a member

invite_member

Email a workspace invitation. Workspace owners only. Grants member or admin, never owner.

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

Input Schema

NameRequiredDescriptionDefault
roleYes
emailYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the owner-only authorization requirement, the side effect of sending an email, and the role ceiling of admin rather than owner. It does not cover duplicate-invite behavior or invitation expiry, but the annotations already mark the tool as non-destructive and non-idempotent.

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?

Three short sentences front-load the action, permission requirement, and role boundary with no wasted wording. Every clause contributes useful information.

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?

The definition covers the main action and authorization boundary for a simple invite tool, but it omits duplicate/existing-member behavior and does not clarify routing versus resend or revoke siblings. With no output schema and partial parameter documentation, an agent is left to infer some operational details.

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

Parameters2/5

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

Schema coverage is only 33%, and the description does not explain email format, workspace_id sourcing, or role semantics beyond what the enum already says. The phrase 'never owner' reinforces the role constraint, but the other two required parameters remain undocumented by the description.

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 action and resource: emailing a workspace invitation, with role constraints. It is clear and concise, but it does not explicitly differentiate itself from related siblings such as resend_invite or revoke_invite.

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 clear context by stating 'Workspace owners only' and limiting grants to member or admin, never owner. It does not state when to use this versus resend or revoke alternatives, so it stops short of full when/when-not guidance.

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