Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

set_read_only_mode

Idempotent

Toggle read-only mode to block all writes or re-enable all write scopes.

Instructions

Quick toggle: enable read-only mode (blocks all writes) or disable it (enables all write scopes). For finer control, use set_write_scopes instead.

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": {
      "enabled": "<enabled>"
    },
    "name": "set_read_only_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledYestrue to enable read-only mode, false to enable all write scopes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations provide idempotentHint and destructiveHint. The description adds behavioral context: it blocks all writes when enabled and enables all write scopes when disabled. This aligns with annotations and adds useful nuance, though it doesn't detail auth requirements or rate limits.

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?

Two sentences, front-loaded with the core purpose, and no extraneous words. Every sentence adds value.

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

Completeness5/5

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

For a simple tool with one boolean parameter, no output schema, and comprehensive annotations, the description provides all necessary context: what it does, when to use it, and an alternative. Nothing missing.

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?

The single parameter 'enabled' has a clear description in the schema (100% coverage). The tool description repeats this same meaning without adding extra nuance, so baseline 3 is appropriate.

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 clearly states the tool toggles read-only mode on/off, blocking or enabling all writes. It uses a specific verb+resource ('toggle read-only mode') and distinguishes itself from 'set_write_scopes' which offers finer control.

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

Usage Guidelines5/5

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

The description explicitly says 'Quick toggle' for a fast mode switch and advises using 'set_write_scopes instead' when finer control is needed, providing clear when-to-use and when-not-to-use guidance.

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