Skip to main content
Glama

Что встало после смены тарифа

get_quiz_tariff_pause
Read-onlyIdempotent

Показывает, что у опроса не работает из-за тарифа: в какие интеграции ответы не уходят (paused — с какого момента и сколько ответов не отправлено; у email_recipients — сколько адресов не получают письмо) и что выключено у опубликованного опроса (off: счётчики yaMetrika, googleStats, vkPixel, fbPixel, свой домен domain, скрытие копирайта copyright, свой логотип logo, незавершённые ответы incomplete, приём оплаты payment). После оплаты в resumable — интеграции, куда можно дослать накопившиеся ответы: это делает resolve_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>"
    },
    "name": "get_quiz_tariff_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description correctly spends its words on semantics instead: the meaning of 'paused' (since when, how many answers unsent), per-field meaning for email_recipients, the list of 'off' flags, and the 'resumable' group. It also discloses the important side-fact that answers are retained and defines the empty-result case as 'quiz works fully'. It stops short of describing response shape/ordering precisely, but the extra context is substantial.

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?

Front-loaded with the core purpose, then the paused/off/resumable breakdown, then the terminal clarifying facts. The long parenthetical enumeration of flags is dense but every listed item is information an agent would otherwise have to guess. Slightly overpacked for a single paragraph, but nothing is filler.

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?

There is no output schema, so the description must carry the return semantics, and it does: three result groups (paused, off, resumable), the per-item meaning within paused, the enumerated off flags, and the empty-result interpretation. Combined with annotations covering safety, an agent has everything needed to call and interpret it.

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?

Only one parameter (quiz_id) exists and schema coverage is 100%, so the schema already carries its meaning. The description adds nothing about quiz_id itself (e.g., where to obtain it or error behavior for unknown IDs), so this sits at the baseline.

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 specific verb and resource ('Показывает, что у опроса не работает из-за тарифа') and enumerates the exact categories inspected: paused integrations, disabled published-quiz features, and resumable integrations. It is clearly separable from resolve_quiz_tariff_pause, which is named as the actor that performs the resumption rather than the diagnosis.

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?

Usage context is explicit: call this after a tariff change to see what stopped, and use resolve_quiz_tariff_pause to actually push accumulated answers. The boundary between diagnosing and fixing is stated outright. There is no explicit 'when not to use' or prerequisite/permission statement, which keeps it from a 5.

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