Skip to main content
Glama

Пароли к закрытому опросу

manage_quiz_passwords
Destructive

Ведёт список паролей доступа к закрытому опросу: показывает заведённые, добавляет новые, заменяет и удаляет. Пароли хранятся хешами, поэтому прочитать заведённый пароль нельзя ни здесь, ни в конструкторе — только заменить новым. В списке видны номер и дата: по номеру в ответах автор узнаёт, кто из приглашённых отвечал. Сама проверка пароля на входе включается настройкой use_password в update_quiz_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>",
      "action": "<action>"
    },
    "name": "manage_quiz_passwords"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: list — показать список, add — добавить, update — заменить пароль, delete — удалить.
quiz_idYesID опроса.
passwordNoПароль. Обязателен для update — это новое значение взамен прежнего. Для add его можно передать вместо списка passwords, если пароль один.
passwordsNoСписок паролей для add, до 50 штук за раз. Нужно больше — вызовите несколько раз: пароль хешируется, и большая пачка не успела бы обработаться.
password_idNoID пароля из list. Нужен для update и delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/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, but the description adds a genuinely non-obvious behavioral fact: passwords are stored as hashes, so an existing password can never be read back here or in the constructor — only replaced. It also explains that the list exposes a number and date used to identify which invitee answered, which is behavioral context the annotations cannot convey. It stops short of stating that delete is permanent or what add/update return.

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?

Purpose and the full action set are front-loaded in the first sentence, and each subsequent sentence carries a distinct fact (hash irreversibility, list fields, where the gate is enabled). It is dense but nearly waste-free; the only borderline redundancy is restating the action list that the enum already enumerates.

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?

With no output schema, the description does the work of describing what list returns (number and date) and what cannot be returned (the plaintext password), which covers the main agent questions. It does not say what add/update/delete respond with or how partial failures in a batch are reported, leaving a small gap for a destructive multi-action tool.

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 adds meaning beyond the schema: it explains that the password_id visible in list is what ties an answer back to an invited respondent, and reinforces that update takes a new value rather than the old one. That reframes password_id from a mere integer into a respondent identifier, which is real added value.

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 opens with a specific verb+resource ("Ведёт список паролей доступа к закрытому опросу") and enumerates the four supported operations: list, add, replace, delete. It also draws a clean boundary against the sibling update_quiz_settings by stating that the actual login check is toggled there via use_password, so an agent can distinguish the two tools without opening either 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?

Each action's effect is stated (list shows, add creates, update replaces, delete removes), and the definition explicitly routes the related-but-different task of enabling the password gate to update_quiz_settings. What's missing is explicit when-not guidance — e.g. that delete is irreversible or that this tool is not the place to change the quiz's closed/open state.

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