Skip to main content
Glama

Состав вопросов в письме

set_quiz_email_questions
Destructive

Задаёт, какие вопросы не попадают в письма. По умолчанию письмо содержит все вопросы и ответы на них, здесь перечисляются исключения — например, чтобы не слать в почту персональные данные или служебные поля. Списки независимы: письмо автору и копия респонденту могут скрывать разное. Передаётся полный список исключений, а не добавка: пустой список возвращает в письмо все вопросы.

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": "set_quiz_email_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
owner_excluded_questionsNoUUID вопросов, которые не попадут в письмо автору. Не передавайте поле, чтобы оставить текущий список.
client_excluded_questionsNoUUID вопросов, которые не попадут в копию респонденту.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known; the description adds the crucial piece the annotations cannot convey — that the passed list is a full replacement, not an increment, and that an empty list restores all questions. It does not mention permission requirements or what happens with unrecognized question UUIDs, but the replacement semantics are the key behavioral disclosure.

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?

Four short sentences, front-loaded with the action, then default behavior, then the independence of the two lists, then the replacement rule. Each sentence carries distinct information with no repetition of the title or schema.

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 destructive mutation with no output schema, the description covers purpose, defaults, replacement semantics, and the two independent lists, which is enough to call it correctly. Only error and permission behavior is left unstated, a minor gap given the rich annotations and schema.

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 the baseline is 3, but the description genuinely adds semantics the schema lacks: the full-replacement rule and the fact that an empty array means 'show everything', whereas the schema only documents the omit-the-field case. It does not spell out per-parameter meaning (owner vs client list), leaving that to the well-documented schema.

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?

The description states a precise verb-plus-resource ('sets which questions do not get into emails') and frames it as an exception list rather than a general email-settings tool, which separates it from siblings such as save_quiz_email_template or get_quiz_email_settings. The negative framing ('which questions are excluded') is unambiguous about what is being set.

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 a clear when-to-use rationale (to keep personal data or service fields out of email) and explains the two independent lists for author vs respondent copies, which is real context for choosing this tool. It does not name an alternative tool for hiding questions elsewhere, but the usage conditions are otherwise explicit.

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