Skip to main content
Glama

Подтверждение адреса получателя

confirm_quiz_email_recipient

Подтверждает адрес получателя копий ответов кодом из письма. Пока адрес не подтверждён, он писем не получает вовсе — add_quiz_email_recipient только заводит его. Код приходит на сам адрес, прочитать его ассистент не может: попросите человека продиктовать. Попыток ограниченное число, поэтому есть и повторная отправка кода.

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

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: confirm — подтвердить кодом, resend_code — выслать код заново.
quiz_idYesID опроса.
email_idYesID адреса из get_quiz_email_settings.
confirmation_codeNoКод из письма. Нужен для confirm.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false), the description discloses the real behavioral constraints: unconfirmed recipients get no mail at all, the code is delivered out-of-band and cannot be read by the assistant so a human must dictate it, and the number of attempts is limited. These are exactly the facts an agent needs before invoking a human-in-the-loop confirmation.

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 compact sentences, front-loaded with the action and immediately followed by the consequence of not confirming. Every sentence carries information; only the resend clause is slightly compressed into the last sentence.

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 mutation tool with no output schema and an open-world side effect, the description covers the side effect, the blocking precondition, the human dependency, and the retry mechanism. Only the return shape of a successful confirm is unstated, which is a minor gap.

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; the description adds genuine meaning by explaining where confirmation_code comes from (a human reading the address's inbox) and why resend_code exists (limited attempts). quiz_id and email_id are left entirely to the schema, which is acceptable given its coverage.

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 names a specific verb and resource ('Подтверждает адрес получателя копий ответов кодом из письма') and explicitly contrasts it with the sibling add_quiz_email_recipient, which 'только заводит его'. An agent can distinguish this from the creation tool 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?

It states the condition for use (the address receives nothing until confirmed) and points to the alternative path (add_quiz_email_recipient creates, resend_code re-issues the code). There is no explicit 'when not to use' guidance, but the selection logic is clear.

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