Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

export_all_questionnaire_versions

Export all imported versions of a questionnaire by specifying its ID or title. Set output directory, format, and interview status to generate data for each version.

Instructions

Start exports for all imported versions of a questionnaire title or ID.

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": {
      "questionnaire_id_or_title": "<questionnaire_id_or_title>"
    },
    "name": "export_all_questionnaire_versions"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo
output_dirNo
export_typeNoSTATA
interview_statusNoAll
questionnaire_id_or_titleYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates an export-starting action but does not mention whether jobs are queued, how progress or results are reported, whether previous exports are overwritten, or what permissions are needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no filler and the core action is front-loaded. However, it is syntactically awkward ('versions of a questionnaire title or ID') and too terse to serve as an adequate spec for a five-parameter tool.

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

Completeness2/5

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

There is no output schema, no annotation coverage, and no parameter documentation. The description explains neither what happens after exports are started, how to monitor or retrieve them, nor how to set the remaining parameters, leaving an agent with significant guesswork.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all parameters. It only hints at the meaning of questionnaire_id_or_title via 'title or ID'; profile, output_dir, export_type, and interview_status are left unexplained beyond their bare names and defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Start exports') and a clear resource scope ('all imported versions of a questionnaire title or ID'). It does not name or contrast any sibling tool, but the scope is concrete enough to distinguish it from tools like export_all_formats or export_and_combine_questionnaire_versions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No explicit guidance is given about when to use this tool vs. the many export-related siblings. The phrase 'all imported versions' implies a use case, but there is no when-to-use, when-not-to-use, or alternative recommendation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools