Survey Solutions MCP Server

Overview Schema Source Related Servers Discussions Admin

create_assignment

Create Survey Solutions assignments, including open web interview links by setting web mode and unlimited quantity. Requires fieldwork write or admin write permission.

Instructions

Create a Survey Solutions assignment. Can create open web interview links by setting web_mode true and quantity -1. Requires fieldwork_write or admin_write permission.

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": {
      "responsible": "<responsible>",
      "questionnaire_identity": "<questionnaire_identity>"
    },
    "name": "create_assignment"
  }
}

Input Schema

Name	Required	Description
`email`	No
`profile`	No
`comments`	No
`password`	No
`quantity`	No	Use -1 for unlimited/open web-link style assignments.
`web_mode`	No
`responsible`	Yes	Responsible user login or user ID. If a login is supplied the HQ endpoint resolves it; if ambiguous, use an exact user ID from list_supervisors/list_supervisor_interviewers/get_user.
`target_area`	No
`identifying_data`	No
`protected_variables`	No
`questionnaire_identity`	Yes	Questionnaire identity in GUID$Version format.
`is_audio_recording_enabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.7Aug 31, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It usefully discloses the permission requirement and the special web_mode/quantity -1 behavior. However, it does not describe output behavior, side effects, or consequences of unspecified parameters, which matters for a creation operation.

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 two tight sentences with no filler. The primary action comes first, followed by the special capability and permission requirement, making it easy to scan.

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?

This is a complex 12-parameter tool with no annotations and no output schema, yet the description provides only minimal context. It leaves many optional parameters, expected behavior, and alternatives unexplained, so an agent cannot safely infer full usage.

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 only 25%, so the description must compensate. It adds meaning for web_mode and quantity by explaining the open-web-link use case, but 12 parameters exist and most remain unexplained in both schema and description. This is partial compensation at best.

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 states the tool creates a Survey Solutions assignment, naming a specific verb and resource. It also highlights the special open-web-link capability, which helps define the tool's scope. However, it does not explicitly distinguish this tool from the sibling create_external_test_link.

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?

The description gives no guidance on when to use this tool versus alternatives such as create_external_test_link or other assignment-related tools. It mentions required permissions, which is contextual, but not when to choose or avoid this tool.

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

Deploy Server