Skip to main content
Glama
Sign In
Qualtrics MCP Server

Qualtrics MCP Server

by yrvelez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_quota

Creates a survey quota using a complete Qualtrics quota definition, with optional assignment to a quota group.

Instructions

Create a quota from a complete raw Qualtrics quota definition. Optionally add it to a quota group in the same operation.

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": {
      "surveyId": "<surveyId>",
      "quota": "<quota>"
    },
    "name": "create_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault
quotaYesComplete Qualtrics quota payload; supports all fields such as Name, Occurrences, Logic, QuotaAction, schedules, and action options
surveyIdYesThe Qualtrics survey ID
quotaGroupIdNoOptional quota group ID to add the new quota to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

Minimal behavioral context beyond the destructiveHint=false annotation. Does not disclose side effects, error conditions, or complexities of the 'raw definition' requirement.

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?

Extremely concise: two brief sentences that communicate the main action and an optional feature without extraneous words.

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?

Adequate for a simple create operation but lacks details on return values (no output schema) and behavior when adding to a quota group. Could be more complete given the complex nested parameter.

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 100% with detailed parameter descriptions. The description adds little new meaning beyond the schema, only reiterating the 'raw definition' concept.

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?

Description clearly states the verb 'create', the resource 'quota', and distinguishes from sibling tools like update_quota or delete_quota by specifying 'from a complete raw Qualtrics quota definition' and optional group addition.

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 explicit guidance on when to use this tool versus alternatives such as update_quota or list_quotas. No prerequisites or conditions are mentioned.

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