Skip to main content
Glama

Удаление получателя копий

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.
email_idYesID адреса (из get_quiz_email_settings).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is structured. The description adds almost nothing beyond that: it does not say the removal is irreversible, what happens to an already-removed address (relevant given idempotentHint=false), or which notification set is affected. Only the vague "author notifications" scoping is new information.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no filler and the action front-loaded, which is good structure. But the brevity comes at the cost of substance rather than being efficient expression of complete information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a destructive mutation with no output schema and no explanation of the result or side effects beyond a one-clause summary. For a delete operation, an agent needs to know irreversibility and scope, and the definition provides neither.

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%, and the schema already explains both quiz_id and email_id, including the pointer to get_quiz_email_settings. The description contributes no additional parameter meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ("Убирает") and an object ("адрес") tied to author notifications, so the general action is inferable. However, it never names the quiz context or the notion of a copy recipient that the title conveys, and it does not distinguish itself from siblings such as toggle_quiz_email_recipient or add_quiz_email_recipient, so an agent must guess at the exact resource.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus the add/toggle/confirm recipient siblings, and no prerequisites (e.g. that the recipient must exist or that the address came from get_quiz_email_settings). Usage is only implied by the verb.

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