Skip to main content
Glama

Письма опроса вкл и выкл

toggle_quiz_email

Включает или выключает письма опроса: owner — уведомление автору о новом ответе, client — копия ответа респонденту. Копия респонденту доступна не на всех тарифах. Повторный вызов с тем же значением ничего не меняет.

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>",
      "type": "<type>",
      "enabled": "<enabled>"
    },
    "name": "toggle_quiz_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesowner — письмо автору, client — копия респонденту.
enabledYestrue — включить, false — выключить.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

The description does add genuine context beyond the annotations, notably the plan restriction "Копия респонденту доступна не на всех тарифах" and the no-op-on-repeat behavior. But that latter sentence ("Повторный вызов с тем же значением ничего не меняет") conflicts with the declared idempotentHint=false, and the description never says what happens if the client channel is unsupported on the current tariff (error vs. silent ignore).

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?

Three short sentences, front-loaded with the action, then the channel definitions, then the caveats. The owner/client gloss partially duplicates the schema's enum descriptions, but the rest of the text earns its place.

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

Completeness3/5

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

With annotations present and no output schema, the description covers the main behavioral edges: scope per channel, tariff gating, and repeat-call behavior. It still leaves open what the tool returns and how failures (unsupported plan, unknown quiz_id) surface, which matters for a mutation tool with openWorldHint=true.

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 description coverage is 100%, with the enum values already documented inline, so the schema carries the parameter burden. The description largely repeats those enum meanings, adding only the tariff caveat for `client`; it adds little semantic detail about `quiz_id` or the `enabled` flag beyond what the schema states.

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 names a specific verb and resource ("Включает или выключает письма опроса") and then enumerates the two notification channels it controls: "owner — уведомление автору о новом ответе, client — копия ответа респонденту". This is enough to separate it from recipient-management siblings like toggle_quiz_email_recipient, though it never explicitly says so.

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 by the channel enumeration (use it to turn author or respondent mail on/off) and the note "Повторный вызов с тем же значением ничего не меняет" tells the agent that re-calling is harmless. However, there is no explicit when-to-use versus when-not-to-use guidance and no routing to alternatives, so an agent must infer the boundaries itself.

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