Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

list_supervisor_interviewers

Retrieve interviewers assigned to a specific supervisor in Survey Solutions. Provide supervisor ID and optional pagination to get the full list.

Instructions

List interviewers assigned to a supervisor.

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": {
      "supervisor_id": "<supervisor_id>"
    },
    "name": "list_supervisor_interviewers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional page size.
queryNoAdvanced/raw endpoint query values. Top-level offset/limit are merged into this object.
offsetNoOptional page offset. For this Survey Solutions endpoint, offset 0 is normalized to 1 to avoid HQ 500 responses observed on some builds.
profileNo
supervisor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

C2.9/5.0
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure, but it only restates the basic operation. It does not describe pagination behavior, response shape, permissions, or server quirks; the offset normalization detail is relegated to the schema rather than the description.

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?

The description is a single front-loaded sentence with no filler or redundant phrasing. It is appropriately concise for a simple list operation, though it is terse enough that it omits useful context covered under other dimensions.

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?

With no output schema and no annotations, the description is incomplete for an agent to call the tool confidently. It does not explain what the returned interviewer objects contain, how pagination works, how the query object merges with limit/offset, or what profile is expected.

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 coverage is 60%, and the description itself provides no direct parameter documentation. However, the phrase 'assigned to a supervisor' does clarify the required supervisor_id meaning. The optional profile and query parameters remain unexplained by the description.

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 names a specific verb ('List') and a specific resource ('interviewers assigned to a supervisor'), making the core operation clear. It is broadly distinguishable from siblings like list_supervisors or get_interviewer, but it does not explicitly contrast with them or mention scope exclusions.

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 guidance is given for when to use this tool versus alternatives such as list_interviews, list_supervisors, or get_interviewer. There is also no mention of prerequisites like needing a valid supervisor_id or an active profile.

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