Skip to main content
Glama

Приглашение участника

invite_workspace_member

Приглашает человека в аккаунт: на указанный адрес уходит письмо со ссылкой. До перехода по ссылке участник виден в списке, но доступа у него нет. Роль задаёт, что он сможет делать, список папок — какие опросы увидит; пустой список открывает все папки. Число участников ограничено тарифом.

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

Input Schema

NameRequiredDescriptionDefault
nameYesИмя участника в списке аккаунта.
emailYesПочта приглашаемого — на неё уйдёт письмо со ссылкой.
commentNoЗаметка о человеке (должность, отдел), видна владельцу аккаунта и тем, кто управляет участниками.
role_idYesID роли (из get_workspace_roles). Роль решает, что человек сможет делать.
folder_idsNoID папок, которые увидит участник. Не передавайте или передайте пустой список, чтобы открыть все папки.
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / name / maxLength
      Added value: +60
  2. Changed1 schema field changed
    • changedInput schema / properties / comment / description
      Previous value: -"Заметка о человеке, видна только владельцу аккаунта."New value: +"Заметка о человеке (должность, отдел), видна владельцу аккаунта и тем, кто управляет участниками."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true for the outbound email), the description discloses the pending-invite state (visible in the list but without access until the link is followed), the role's effect on permissions, the folder-list semantics where an empty list unlocks everything, and a tariff-based member cap. These are meaningful side effects and constraints an agent cannot infer from the structured fields.

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?

Four compact sentences, front-loaded with the core action and consequence, with zero filler. Density is high but each clause carries distinct information (email, pending state, role, folders, quota).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter creation tool with full schema coverage and no output schema, the description covers the external side effect, the resulting state, permission scoping, and the tariff limit. Nothing essential to correct invocation is missing, and return values need not be explained.

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 100%, so the baseline is 3, but the description goes slightly beyond by tying role to capability and by restating the empty-folder-list behavior in plain language rather than relying on the JSON field text. It does not add format or syntax details beyond what the schema already supplies.

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 verb and resource (invite a person into the account) plus the mechanism (an email with a link is sent to the address). It is clearly distinct from resend_workspace_member_invite by describing the initial send rather than a repeat, though it never names that sibling explicitly.

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 context is implied rather than stated: the description explains that the invitee stays pending until clicking the link, which hints at when to use it versus a resend or role-editing tool. It contains no explicit 'use this when… instead of…' routing against the many sibling member-management tools.

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