Skip to main content
Glama

Настройки писем опроса

get_quiz_email_settings
Read-onlyIdempotent

Возвращает настройки писем опроса: включены ли уведомление автору и копия респонденту, список адресов автора с их состоянием подтверждения и шаблоны писем. Адрес работает только после подтверждения кодом из письма (в настройках писем опроса в кабинете) — это поле «checked».

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the returned address list carries per-address confirmation state, and an address only functions after code confirmation, which is what the "checked" field reflects. That explains a non-obvious field semantic the agent would otherwise misread.

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?

Front-loaded with the verb and the enumeration of returned data, then a second sentence for the one non-obvious rule about confirmation. No filler, though the confirmation sentence is slightly convoluted with the parenthetical cabinet reference.

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?

No output schema exists, so the description carries the return-value burden and does so by naming the three returned components, including the confirmation-state detail. For a single-parameter read tool with full annotation coverage this is essentially complete; only the shape of the template objects remains unspecified.

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?

There is a single parameter, quiz_id, and schema description coverage is 100%, so the schema already fully documents it. The description adds no scoping, format or source detail for quiz_id beyond what the schema states, so the baseline 3 applies.

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 ("Возвращает настройки писем опроса") and then enumerates the returned parts: author notification/respondent copy flags, author address list with confirmation state, and email templates. An agent can tell this is the read counterpart to save_quiz_email_notifications. It stops short of naming a sibling explicitly, so it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the read-only framing of "Возвращает" — there is no explicit "use this when you need to inspect before calling save_quiz_email_notifications / confirm_quiz_email_recipient" guidance and no exclusions. The resource naming makes the intent inferable, but the agent must decide on its own when to read vs. mutate.

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