Skip to main content
Glama

Дослать ответы после оплаты

resolve_quiz_tariff_pause
Destructive

После оплаты тарифа досылает ответы, которые за паузу не ушли в интеграции, или отказывается от них. resend ставит в очередь все пропущенные ответы выбранных интеграций (не старше 90 дней), начиная с самых ранних, как обычную отправку; удалённые, скрытые по лимиту ответов, отклонённые модерацией и с жалобой не досылаются. dismiss помечает пропуски отклонёнными — дослать их больше не предложат. Что можно дослать — в resumable у get_quiz_tariff_pause. Досылка отправляет сообщения и письма живым людям: спросите пользователя перед вызовом.

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>",
      "uuids": "<uuids>"
    },
    "name": "resolve_quiz_tariff_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidsYesКлючи интеграций из get_quiz_tariff_pause. email_recipients можно только отклонить.
actionYesresend — дослать, dismiss — не досылать.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructive/openWorld annotations, it discloses concrete side effects: the call sends messages and emails to live people, requires user confirmation, only covers answers up to 90 days old, and silently excludes deleted, limit-hidden, moderation-rejected, and complained-about answers. It also clarifies the irreversibility of dismiss.

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?

The most important fact, that this sends real messages to real people and needs confirmation, is placed last but is unmissable, and the resend/dismiss semantics are front-loaded. Slightly long single block, but each sentence carries distinct operational information.

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

Completeness5/5

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

For a three-parameter mutation tool with no output schema, the description covers preconditions, per-action behavior, exclusion rules, irreversibility, and the human-impact warning. An agent has everything needed to call it safely and correctly.

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 the parameter meanings, enum values, and the email_recipients restriction are already documented in the schema. The description adds behavioral context around the 90-day window and processing order but no new syntax or format detail for the three parameters themselves.

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 gives a clear verb pair (resend / dismiss) on a specific resource (answers missed during a pause in integrations) and names the read-only sibling get_quiz_tariff_pause as the place to discover what is resumable. An agent can distinguish this mutation tool from the query 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 Guidelines5/5

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

It states the condition that selects each action: resend queues all missed answers starting from the earliest, dismiss marks gaps as rejected so they are no longer offered. It also names the prerequisite source (resumable from get_quiz_tariff_pause) and imposes an explicit confirmation requirement before calling.

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