Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

download_interview_pdf

Download a single interview's PDF transcript to a local file path on the host machine by specifying the interview ID and output location.

Instructions

Download the PDF transcript for one interview to a local file path on the MCP host.

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": {
      "interview_id": "<interview_id>"
    },
    "name": "download_interview_pdf"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo
output_pathNo
interview_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It does reveal that a file is written to a local host path, but it does not state whether existing files are overwritten, whether directories must exist, or whether any interview state or permission prerequisites apply.

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?

The description is a single sentence with the action, resource, and destination front-loaded. Every word earns its place; there is no filler or redundant restating of the tool name.

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?

For a 3-parameter tool with no schema descriptions, no annotations, and no output schema, this description is not complete enough. It explains what the tool does but not how an agent should supply valid values for profile and output_path, nor what result to expect.

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. It loosely maps 'one interview' to interview_id and 'local file path' to output_path, but it leaves the profile parameter completely unexplained and provides no path format, file extension, or optionality guidance.

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 uses a specific verb ('Download'), a precise resource ('PDF transcript for one interview'), and a clear destination ('local file path on the MCP host'). This distinguishes it from broader siblings like download_export_file or export_all_formats.

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 phrase 'for one interview' implies this is for single-interview PDF retrieval rather than bulk or multi-format exports. However, it never names alternatives or states when not to use this tool, leaving usage context implicit rather than explicit.

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