Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

inspect_export_file

Inspect a Survey Solutions export zip to list files, classify data types, and preview text metadata or sample rows without parsing binary Stata/SPSS data.

Instructions

Inspect a downloaded Survey Solutions export zip on the MCP host. Lists files, classifies data/comment/action/DDI/preview files, and samples lightweight text/tabular metadata without parsing binary Stata/SPSS data.

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": {
      "export_path": "<export_path>"
    },
    "name": "inspect_export_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
extractNoWhen true, unpack files to output_dir or a sibling *_unpacked folder.
output_dirNoDestination folder for extraction when extract is true.
export_pathYesAbsolute or working-directory-relative path to a downloaded Survey Solutions export zip.
sample_rowsNoNumber of sample data rows to return for CSV/TAB/TSV files, capped at 25.
max_text_bytesNoMaximum text-like file size to preview or sample.
include_detailsNoWhen true, include detailed per-file previews, missingness, and distributions. Default false keeps responses small.
include_samplesNoWhen true, include sample rows in compact tabular summaries. Default false keeps responses small.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It transparently discloses that it avoids parsing binary Stata/SPSS data, which is genuinely useful, but it omits the side-effect that the extract parameter can unpack files into output_dir or a sibling folder. The 'inspect' framing could misleadingly suggest a purely read-only operation despite a write-capable extract mode.

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

Conciseness5/5

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

A single, dense sentence conveys the tool's purpose, scope, operations, and a key limitation without filler. Every clause earns its place and the core action is front-loaded.

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

Completeness3/5

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

The description covers the main purpose well but is incomplete for a 7-parameter tool with no annotations and no output schema. It does not describe the returned preview/summary structure, and it fails to mention the extract side-effect that writes files, which an agent needs to anticipate before invoking the tool.

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 schema already documents all seven parameters thoroughly. The description adds general context about listing and sampling metadata, but it does not add meaning beyond the schema for extract, output_dir, sample_rows, include_details, or other parameters, matching the baseline.

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 clearly identifies the specific verb and resource: inspect a downloaded Survey Solutions export zip on the MCP host. It enumerates concrete actions (list files, classify file types, sample metadata) and explicitly excludes binary Stata/SPSS parsing, which distinguishes it from export and download siblings, though it never names those alternatives directly.

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

Usage Guidelines3/5

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

The description implies the tool is for post-download, pre-analysis inspection of a local export zip, but it does not explicitly state when to choose it over related tools like download_export_file, export_all_formats, or prepare_latest_export_for_analysis. The context is clear but exclusionary guidance is left to inference.

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