Skip to main content
Glama

Участник аккаунта в получатели

add_quiz_email_team_member

Добавляет в «Кому» писем опроса адрес участника аккаунта — сразу подтверждённый, без кода: адрес подтверждён аккаунтом. Только участник, принявший приглашение (get_workspace_members со status = 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": {
      "quiz_id": "<quiz_id>",
      "user_id": "<user_id>"
    },
    "name": "add_quiz_email_team_member"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
user_idYesuser_id участника (из get_workspace_members).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses two meaningful behaviors: the address is added already confirmed with no verification code, and the number of addresses is capped by the tariff plan. It does not address what happens on duplicate adds, which matters given idempotentHint=false, but the core behavioral context is supplied.

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?

Three sentences, front-loaded with the action and its key behavioral distinction, then the eligibility rule and the limit. The parenthetical 'адрес подтверждён аккаунтом' restates the preceding clause and is the only real redundancy.

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 mutation with no output schema and annotations already covering the safety profile, the description supplies the prerequisite, the confirmation behavior, and the plan cap. It stops short of describing the result of a successful add or duplicate handling, which would close the remaining gap.

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 both quiz_id and user_id are already documented in the schema, including that user_id comes from get_workspace_members. The description reinforces that source and adds the active-status constraint, but adds little else about parameter meaning beyond the schema, which fits the baseline.

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 gives a specific verb and resource: adding an account member's address to the 'To' field of quiz emails, and it states the distinguishing trait that this address is already confirmed via the account rather than requiring a code. This implicitly separates it from the generic add_quiz_email_recipient, though that sibling is never named explicitly.

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 a clear prerequisite: only a member who accepted the invitation (get_workspace_members with status = active) can be added, and it names the tool used to obtain that id. It does not spell out when to prefer add_quiz_email_recipient instead, so the exclusion is left implicit.

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