Skip to main content
Glama

Export answers to SPSS

export_answers_spss
Read-onlyIdempotent

Exports quiz answers to the SPSS format (.sav) — the same data as CSV and XLSX, in a shape statistical packages open. Link parameters go into the file alongside the answers, otherwise some columns would be left unnamed. Returns a download link valid for one hour. Exporting results is not available on every plan.

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
idsNoExport only these answers by ID.
quiz_idYesQuiz ID.
is_deletedNoTake answers from the trash instead of the regular ones.
excludedIdsNoExclude these answers by ID.
is_completeNoCompleted responses only. Defaults to yes.
is_screenoutNoInclude screened-out respondents.

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.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, and the description goes further: it discloses that link parameters are embedded into the file, that the returned download link expires after one hour, and that a plan-level entitlement gates the call. Remaining gaps (file-size limits, any async/queueing behavior) are minor.

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?

Three sentences, front-loaded with format and purpose, then behavior, then the plan caveat. The middle sentence's rationale ('otherwise some columns would be left unnamed') earns its place by pre-empting confusion about unexpected columns, though the wording is slightly indirect.

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?

With no output schema, the description still covers the return value (a download link, valid one hour), the entitlement constraint, and why extra link columns appear. Combined with full schema coverage and annotations, an agent has everything needed to call it 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 description coverage is 100%, so all six parameters are already documented; the description adds no per-parameter meaning (ids vs excludedIds, is_deleted, is_screenout are untouched). Its remark about link parameters appearing as columns explains file content rather than parameter semantics, so the baseline 3 applies.

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, resource and output format: exports quiz answers to SPSS (.sav). It also positions the tool against the CSV/XLSX siblings by saying it is 'the same data ... in a shape statistical packages open', so an agent can pick the format without inspecting other schemas.

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?

Implicit routing guidance is clear (same data as CSV/XLSX, chosen when a statistical-package-readable file is needed), and it adds a real eligibility constraint: 'not available on every plan'. It stops short of explicitly naming the sibling format tools or stating when NOT to use it.

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.