Skip to main content
Glama

Обнуление посещений

reset_quiz_visits
Destructive

Обнуляет посещения опроса: статистика посещений (открытия, уникальные, по дням, источники, устройства, браузеры, страны, журнал посещений) начинается с нуля, как будто опрос никто не открывал. Ответы не трогаются и показывают своё устройство, город и источник как раньше; удалить их — delete_quiz_answers. Вернуть посещения нельзя, поэтому нужен confirm: true. Новые посещения после сброса считаются как обычно.

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>",
      "confirm": "<confirm>"
    },
    "name": "reset_quiz_visits"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesОбязателен и должен быть true: подтверждение, что посещения обнуляются насовсем.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint and non-idempotency, but the description adds substantive context beyond them: precisely which aggregates reset, the fact that answers and their attached device/city/source metadata survive, irreversibility, and that new visits accrue normally after the reset. That is exactly the post-mutation state an agent needs to predict.

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 action and its scope, then the side effect on answers, then the confirm requirement. The sentence chain is long and semicolon-heavy, but every clause carries information an agent would otherwise have to guess.

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 two-parameter destructive tool with no output schema, the description covers what is destroyed, what is preserved, irreversibility, the confirm gate, post-reset behavior, and the nearest sibling alternative. Nothing material is missing.

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 documents both quiz_id and the confirm-must-be-true rule, so the description's mention of 'нужен confirm: true' largely restates structured data. It adds only the rationale (permanence) that the schema also states.

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?

States a specific verb and resource ('Обнуляет посещения опроса') and immediately enumerates the exact statistics affected (opens, uniques, by-day, sources, devices, browsers, countries, visit log), so the scope is unambiguous. It also distinguishes itself from delete_quiz_answers, which handles a different data class.

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?

Explicitly warns that the action is irreversible and requires confirm: true, and routes answer deletion to delete_quiz_answers instead. It does not spell out a positive 'when to use this' scenario (e.g. cleaning test traffic before launch), so it stops just short of full routing guidance.

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