Skip to main content
Glama

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

resend_workspace_member_invite

Отправляет приглашение повторно — когда письмо потерялось или ссылка устарела. Участнику, который уже принял приглашение, письмо не отправляется.

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

Input Schema

NameRequiredDescriptionDefault
member_idYesID участника (member_id из get_workspace_members).
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already disclose openWorldHint=true (external email dispatch) and idempotentHint=false, and the description adds a genuine behavioral fact not in them: no message is sent to a member who already accepted the invite. It stops short of stating permission requirements or what the caller observes on success versus failure.

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 no filler: the action first, then the practical situation, then the one edge case. Every clause carries meaning.

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 two-parameter action with full schema coverage and annotations covering safety and world scope, the description supplies what structured fields cannot — the trigger situation and the suppression rule. Only the caller-visible outcome is left unstated, and no output schema exists to cover it.

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 100%, with both member_id and workspace_id documented in-schema including where each value comes from. The description adds nothing about the parameters, so the baseline 3 applies.

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 ('Отправляет приглашение повторно'), making the re-send operation unambiguous. The 'повторно' framing implicitly separates it from the initial invite, but it never names invite_workspace_member as the sibling it complements, so sibling differentiation is only implied.

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 explicit trigger conditions: use when the email was lost or the link expired. It also supplies one exclusion — a member who already accepted will not receive mail — though this is framed as behavior rather than as 'do not call in this case', leaving the agent to infer the routing decision.

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