Skip to main content
Glama

Правила, сводка и события писем

save_quiz_email_notifications
Destructive

Меняет «Уведомления» опроса сверх писем: правила (отдельное письмо, когда ответ подходит под условия), сводку раз в день или неделю, события (каждые N ответов, опрос закрылся, израсходован процент ответов тарифа, нет ответов N дней), напоминание респонденту, который не закончил, и баллы в письме респонденту. Передавайте только то, что меняете; правила заменяются списком целиком. Адресаты — email_id из recipients в get_quiz_email_settings, письма уходят только на подтверждённые адреса. Текущие значения — поле notifications в get_quiz_email_settings.

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

Input Schema

NameRequiredDescriptionDefault
rulesNoПравила, до 20. Список заменяет текущий целиком; пустой список удаляет все правила.
digestNoСводка: сколько новых ответов, средний ответ по оценкам и числам, свежие текстовые ответы. За период без ответов не приходит.
eventsNoСобытия опроса. email_ids — общий список адресатов для всех событий.
quiz_idYesID опроса.
client_reminderNoНапоминание респонденту, который начал опрос, оставил адрес и не закончил. Одно письмо на начатый ответ; ссылка ведёт на опрос.
client_send_scoreNoВ стандартном письме респонденту — «Баллы: N из M». Только у опроса с подсчётом баллов.
client_send_correct_answersNoВ стандартном письме респонденту — верен ли ответ на каждый вопрос и какой правильный. Только у опроса с подсчётом баллов.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description substantiates them: an empty rules list deletes all rules, rules replace the existing set entirely, and unconfirmed/deleted addresses are silently skipped. It also discloses beyond-annotation behavior — digest is not sent for a period with no answers, silence events only repeat after a new answer, the limit event fires once per tariff month, and manual closure is not an event. No contradiction with annotations.

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 sentences, front-loaded with the mutation scope, then the update rule, then the recipient constraint, then the read source — a sensible order. It is dense but earns most of its length on a 7-parameter nested mutation tool; the enumeration of event types mildly duplicates the schema descriptions.

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 destructive, deeply nested mutation tool with no output schema, the description covers what is changed, how partial updates work, replacement/deletion semantics, where ids come from, and per-section delivery caveats. An agent has everything needed to call it correctly and safely.

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 baseline would be 3, but the description adds semantics the schema does not: partial-update behavior ('Передавайте только то, что меняете'), whole-list replacement of rules, and the cross-tool constraint that email_ids must come from recipients in get_quiz_email_settings and only confirmed addresses receive mail. It does not re-explain per-field enums, which the schema already documents well.

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 plus resource ('Меняет «Уведомления» опроса') and then enumerates exactly the sub-surfaces it writes: rules, digest, events, client reminder, and score/correct-answer flags in respondent emails. It is clearly distinguished from the read sibling get_quiz_email_settings and from template/recipient tools, so an agent can select it without opening the schema.

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 concrete operating instructions: send only what you change, and rules are replaced as a whole list. It names get_quiz_email_settings as the source of current values and of email_id recipients, which is real routing guidance. It does not explicitly state when NOT to use this versus toggle_quiz_email or save_quiz_email_template, so it stops short of full exclusion 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