Skip to main content
Glama

Выгрузка в Google Таблицы

manage_quiz_google_sheets
Destructive

Выгрузка ответов в Google Таблицы: что попадает в таблицу и как часто она обновляется. show — состояние: адрес и название таблицы, живой ли доступ, режим обновления, когда выгружали последний раз, какие вопросы исключены. Дальше: включить и выключить выгрузку, убрать интеграцию, задать состав вопросов, переключить метку времени и персональные данные, выбрать режим обновления (сразу, по расписанию в заданный час, вручную), дослать накопившееся и выгрузить все ответы заново. Подключение аккаунта Google и выбор таблицы делают в кабинете: там вход в аккаунт и окно Google Диска. Журнал синхронизаций — в get_quiz_integrations.

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

Input Schema

NameRequiredDescriptionDefault
actionYesЧто сделать: show, activate, deactivate, delete, save_widgets — состав вопросов, save_switchers — метка времени и персональные данные, set_sync_mode — режим обновления, sync_now — дослать накопившееся, export_all — выгрузить все ответы.
quiz_idYesID опроса.
sync_modeNoКогда обновлять таблицу: realtime — сразу после ответа, scheduled — раз в сутки в заданное время, manual — только по команде. Обязателен для action=set_sync_mode; при scheduled нужны ещё schedule_hour и schedule_minute.
export_modeNoКуда выгружать все ответы: new_file — в новый файл, new_sheet — на новый лист, replace — заменить текущий лист. Обязателен для action=export_all.
schedule_hourNoЧас обновления, 0–23. Обязателен для scheduled.
schedule_minuteNoМинута обновления, 0–59. Обязательна для scheduled.
enable_timestampNoДобавлять столбец со временем ответа.
hidden_widget_idsNoID вопросов, которые НЕ попадают в таблицу. Список задаётся целиком: чего в нём нет, то в таблицу вернётся. Взять из quiz://{id}/structure.
enable_personal_dataNoВыгружать персональные данные респондента.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds real context beyond them: removal of the integration, re-export of all answers, pushing the accumulated backlog, and the fact that the excluded-questions list is exhaustive rather than additive. It does not say whether delete is reversible or what export_all/replace does to existing sheet contents, but that gap is partly covered by the schema.

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?

Purpose is front-loaded, then the show contract, then the mutation menu, then external prerequisites. The show enumeration and operation list are dense but each item maps to a schema enum, so little is wasted; slightly heavy for a single paragraph but readable.

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

Completeness4/5

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

For a 9-parameter, destructive, open-world integration tool with no output schema, the definition covers purpose, the show return shape, prerequisites outside the tool, and where the sync log lives. Remaining gaps are edge-case behavior (state before activation, effect of replace on prior data) rather than anything blocking correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the enum meanings are already documented; the description's added value is the show payload ('адрес и название таблицы, живой ли доступ, режим обновления, когда выгружали последний раз, какие вопросы исключены'), which substitutes for the absent output schema. It also reinforces the exhaustive-list semantics of hidden_widget_ids and the three refresh modes.

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 first sentence names a concrete verb and resource ('Выгрузка ответов в Google Таблицы') and the body enumerates every supported operation from show through export_all. It also explicitly routes sync-history requests to the sibling get_quiz_integrations, so an agent can separate the two 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 Guidelines4/5

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

It states the key precondition clearly: Google account connection and spreadsheet selection happen in the cabinet (login + Google Drive window), not through this tool, and that the sync log lives in get_quiz_integrations. It does not spell out when-not-to-use or what state must exist before activate, but the routing guidance is strong.

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