Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_assignment_audio_recording

Retrieve the audio-recording setting for a specific assignment to verify if audio capture is enabled or disabled.

Instructions

Read audio-recording setting for one assignment.

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": {
      "assignment_id": "<assignment_id>"
    },
    "name": "get_assignment_audio_recording"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNo
assignment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, 'Read' at least signals a non-mutating operation. However, it does not disclose error behavior, auth/profile requirements, or what the response will look like, so transparency is only partial.

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?

Seven words, single sentence, front-loaded with verb and object; no waste. It covers the core semantics without filler.

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?

For a simple read, the core call is inferable (assignment_id), but the profile parameter and return value are not described and there are no annotations or output schema to fill the gaps. Adequate for basic usage but not fully complete.

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?

The schema has no descriptions (0% coverage) and the tool text only hints at assignment_id via 'one assignment.' The optional profile parameter is entirely unexplained, so the description does not compensate for the schema gap.

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?

Uses a specific verb ('Read') and resource ('audio-recording setting') scoped to 'one assignment.' This clearly separates it from the write sibling set_assignment_audio_recording and from the questionnaire-level get_questionnaire_audio_recording.

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 reading an assignment-level setting, but it does not explicitly say when to choose it over set_assignment_audio_recording or get_questionnaire_audio_recording, nor does it state exclusions.

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