Skip to main content
Glama

Выгрузка ответов в SPSS

export_answers_spss
Read-onlyIdempotent

Выгружает ответы опроса в формат SPSS (.sav) — тот же набор данных, что в CSV и XLSX, но в виде, который открывают статистические пакеты. Вместе с ответами в файл идут параметры ссылки, иначе часть колонок осталась бы безымянной. Возвращает ссылку на скачивание, действительную час. Выгрузка результатов доступна не на всех тарифах.

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": "export_answers_spss"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsNoВыгрузить только эти ответы по их ID.
quiz_idYesID опроса.
is_deletedNoВзять ответы из корзины вместо обычных.
excludedIdsNoИсключить эти ответы по их ID.
is_completeNoТолько завершённые прохождения. По умолчанию да.
is_screenoutNoВключить отсеянных респондентов.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / excludedIds / maxItems
      Added value: +10000
    • addedInput schema / properties / ids / maxItems
      Added value: +10000
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's job is to add operational detail, which it does: link parameters are embedded as extra columns, the tool returns a download link with a one-hour expiry, and the feature is plan-gated. It does not say whether generation is synchronous or how long a large export takes, which keeps it below the top mark.

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 and format are front-loaded in the first clause, followed by three short sentences each carrying distinct information (extra columns, link expiry, plan restriction). No wasted wording, though the parenthetical format note could be tightened.

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?

With no output schema, the description usefully compensates by describing the return value (a download link valid for one hour) and by explaining why unnamed columns appear. Combined with the plan-gating caveat, an agent has enough to call and interpret it, missing only execution-timing or size-limit details.

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%, so the six input parameters (ids, excludedIds, is_deleted, is_complete, is_screenout, quiz_id) are already documented in the schema and the description adds nothing about their semantics. The remark about link parameters concerns output columns, not inputs, so this stays 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 names a specific verb and resource (export survey answers) plus the exact target format (.sav), and explicitly contrasts it with the CSV and XLSX siblings by stating it is the same dataset rendered for statistical packages. An agent can distinguish it from export_answers_csv or export_answers_xlsx without opening any 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 gives clear selection context — choose this when the consumer is a statistical package, otherwise the CSV/XLSX exports carry the same data — and adds a real prerequisite (not available on all plans). It stops short of explicit 'use X instead when' phrasing, so the routing is strongly implied rather than spelled out.

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