Skip to main content
Glama

Шаблон письма опроса

save_quiz_email_template
Destructive

Задаёт тему и текст писем опроса. Два независимых письма: автору о новом ответе и копия респонденту. Не переданные поля не трогаются. Адрес респондента здесь не задаётся: он берётся из ответа на вопрос или из скрытой переменной, на которую указывает client_source.

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_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
owner_letterNoТекст письма автору, до 5000 символов.
client_letterNoТекст письма респонденту, до 5000 символов.
client_sourceNoОткуда брать адрес респондента: имя скрытой переменной опроса или идентификатор вопроса с почтой.
owner_subjectNoТема письма автору, до 500 символов.
client_subjectNoТема письма респонденту, до 500 символов.
owner_raw_htmlNoПолностью свой HTML письма автору — уходит как есть, без обёртки WebAsk. Работает только с подключённым своим SMTP.
client_raw_htmlNoПолностью свой HTML письма респонденту. Работает только с подключённым своим SMTP.
owner_raw_enabledNoВключить полностью свой HTML для письма автору. Без своего SMTP письмо всё равно уйдёт визуальным шаблоном — инструмент об этом предупредит.
client_raw_enabledNoВключить полностью свой HTML для письма респонденту.
owner_send_promo_codeNoКласть промокод в письмо автору.
client_send_promo_codeNoКласть промокод в письмо респонденту.
owner_formatted_letterNoВизуальный шаблон письма автору: HTML из редактора. Именно он уходит, если не включён стандартный шаблон или режим своего HTML.
owner_reply_to_addressNoАдрес для ответа в письме автору: UUID вопроса, из ответа на который берётся адрес.
owner_use_default_tmplNoИспользовать стандартный шаблон для письма автору.
client_formatted_letterNoВизуальный шаблон письма респонденту: HTML из редактора.
client_reply_to_addressNoАдрес для ответа в письме респонденту: обычный адрес почты.
client_use_default_tmplNoИспользовать стандартный шаблон для письма респонденту.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag this as a non-readonly, destructive write, and the description adds genuinely new behavior: partial-update semantics, the SMTP prerequisite for raw HTML, and the fact that the tool warns when raw HTML is enabled without own SMTP. It does not address the destructive aspect (what existing template content gets overwritten), which is the one behavioral gap left.

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?

Three short sentences, front-loaded with the core action, then the two-letter structure, then the two governing constraints. Nothing is redundant with the schema or annotations, and every sentence carries information.

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 an 18-parameter mutation tool with no output schema, the description covers the highest-risk semantics: partial updates, the address indirection, and the SMTP condition. The remaining gap is template-mode precedence among the formatted/raw/default variants, which the agent still has to derive from parameter descriptions alone.

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?

With 100% schema coverage the baseline is 3, but the description adds cross-parameter meaning the schema only implies: that client_source is the sole conduit for the recipient address and that the owner/client letter pairs are independent. It does not explain the precedence between formatted_letter, raw_html, and use_default_tmpl, which is the most confusing part of the 18-parameter surface.

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?

States a specific verb and resource: sets the subject and body of quiz emails, and immediately splits the resource into two independent letters (author notification and respondent copy). That is far more precise than the name alone. It does not, however, explicitly distinguish itself from the sibling save_quiz_email_notifications, so an agent must infer the boundary.

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 operational context: fields not passed are left untouched (so it is a partial update), and the respondent address cannot be set here but is derived from an answer or hidden variable named in client_source. It stops short of naming an alternative tool or an explicit when-not-to-use condition, so it is clear context rather than full routing 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