Skip to main content
Glama

Получатель копий вкл и выкл

toggle_quiz_email_recipient

Включает или выключает конкретный адрес в уведомлениях автору об ответах (target answers, по умолчанию) или в письмах о новой записи онлайн-записи (target booking). Списки независимы: is_active и is_active_booking в recipients. Работает только с подтверждённым адресом; число адресов для уведомлений об ответах ограничено тарифом, у писем о записи лимита нет.

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

Input Schema

NameRequiredDescriptionDefault
targetNoДля каких писем переключить адрес: answers — уведомления о новых ответах (по умолчанию), booking — письма о новой записи онлайн-записи.
quiz_idYesID опроса.
email_idYesID адреса (из get_quiz_email_settings).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / target
      Added value: +{
      +  "description": "Для каких писем переключить адрес: answers — уведомления о новых ответах (по умолчанию), booking — письма о новой записи онлайн-записи.",
      +  "enum": [
      +    "answers",
      +    "booking"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the operation is a non-read-only mutation that is not idempotent and has no destructive intent. The description adds real value beyond that: a precondition (confirmed address only), a quota distinction between the two lists, and the non-obvious fact that the two activation flags are independent of each other. It does not say what happens on an unconfirmed address or whether the new state is returned, which keeps it below 5.

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?

The purpose and default target are front-loaded in the first sentence, with constraints following. It is dense but readable; references to internal field names (is_active / is_active_booking) are useful yet slightly technical noise for an agent that only needs 'target'.

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 three-parameter mutation with no output schema, the definition covers preconditions, quota behavior, and list independence. The only meaningful omission is the return value or how failures (unconfirmed address, quota exceeded) surface, which an agent may need when chaining calls.

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%, including an enum with a per-value description for 'target', so the schema already documents all three parameters. The description reinforces the default value and the two-list independence, but adds no new syntax, format, or constraint meaning for quiz_id or email_id beyond the schema baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: turning a single address on/off inside two distinct notification lists (answers vs booking). It names the exact per-recipient scope and the mechanism (independent is_active / is_active_booking flags), which clearly separates it from add_quiz_email_recipient, confirm_quiz_email_recipient, delete_quiz_email_recipient, and the quiz-level toggle_quiz_email.

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?

Gives clear operating context: default target is 'answers', 'booking' selects the other list, the address must already be confirmed, and only the answers list is plan-limited. It does not state when to prefer an alternative path (e.g. that adding or removing a recipient is a different tool), so guidance is strong but not fully exhaustive.

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