Skip to main content
Glama
Sign In
Survey Solutions MCP Server

Survey Solutions MCP Server

by lbruce-wq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

hq_unapprove_interview

Revert an approved interview to a non-approved status after confirming its exact interview ID, for HQ fieldwork or admin corrections.

Instructions

Move an HQ-approved interview out of HQ approved state. Requires fieldwork_write or admin_write permission and exact interview ID confirmation. Live mutation; read current status first and use only on a known target case.

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>",
      "confirm_interview_id": "<confirm_interview_id>"
    },
    "name": "hq_unapprove_interview"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNo
profileNo
interview_idYes
confirm_interview_idYesMust exactly match interview_id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.7

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that this is a 'live mutation,' specifies required permissions, and warns about confirmation and precondition checks. This is strong disclosure, though it does not describe side effects or reversibility beyond the state move.

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?

Three dense sentences with no filler. The action, permission requirement, safety warning, and precondition are all front-loaded and clearly separated. Every sentence contributes essential information.

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

Completeness4/5

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

For a mutation tool with no annotations and no output schema, the description covers the essential invocation context: purpose, permissions, confirmation requirement, and a precondition. It is slightly incomplete regarding optional parameters and behavior on mismatch, but the core agent decision path is well supported.

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 only 25%, so the description must compensate. It reinforces the critical confirm_interview_id requirement ('exact interview ID confirmation'), but it does not explain the interview_id, comment, or profile parameters. The description adds safety context but leaves several parameters undocumented.

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 states a clear verb and resource: 'Move an HQ-approved interview out of HQ approved state.' This precisely defines the tool's state-transition purpose and differentiates it from related approval/rejection siblings by naming the specific state change.

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

Usage Guidelines4/5

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

The description gives actionable guidance: requires specific permissions, requires exact interview ID confirmation, and says 'read current status first and use only on a known target case.' It does not explicitly name alternatives, but the preconditions and targeting advice make when-to-use clear.

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