Skip to main content
Glama

Новый получатель копий ответов

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>",
      "email": "<email>"
    },
    "name": "add_quiz_email_recipient"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesАдрес, на который слать уведомления о новых ответах.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 that the address starts inactive, that a verification email is dispatched, and that a plan-based quota limits the number of addresses. That is meaningful side-effect context not present in the structured fields; only the return value or the quota-exceeded error behavior is left unexplained.

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 action, followed by the two facts an agent must know (pending confirmation, quota limit). No filler or repetition.

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 two-parameter mutation tool with no output schema, the definition covers the important behavior: the address is created in an unverified state and requires a follow-up confirmation. Only the response shape and quota-exceeded behavior are omitted, which is minor given the tool's simplicity.

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?

Schema coverage is 100%, so both quiz_id and email are already documented in the schema. The description restates that the address receives answer notifications but adds no format, uniqueness, or duplicate-handling semantics beyond the schema, 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?

The description states a concrete verb and resource: it adds an email address that receives notifications about new responses to the quiz author. The pending-confirmation detail implicitly separates it from confirm_quiz_email_recipient and toggle_quiz_email_recipient, though no sibling is named.

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 implied rather than stated: an agent learns the recipient will not work until the code is confirmed, which hints that a confirmation call must follow. It never names confirm_quiz_email_recipient or states when to prefer add_quiz_email_team_member instead.

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