LimeSurvey MCP Server

Delete quota

limesurvey_delete_quota

Destructive

Delete a survey quota. Requires confirm_destructive_action=true.

Instructions

Delete a survey quota. Requires confirm_destructive_action=true.

Calls LimeSurvey RemoteControl method delete_quota. Authentication uses the configured service account; do not provide a session key.

Input Schema

Name	Required	Description	Default
`quota_id`	Yes	Numeric quota ID.
`response_format`	No	Output format. JSON preserves the complete structured result; Markdown is optimized for reading.	json
`confirm_destructive_action`	Yes	Required acknowledgement of the permanent deletion.

Output Schema

Name	Required	Description	Default
`method`	Yes
`result`	Yes
`warnings`	No
`truncated`	No
`truncation_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.0Oct 14, 2026

addedOutput schema / properties / warnings

Added value: +{
+  "items": {
+    "$ref": "#/definitions/__schema0"
+  },
+  "type": "array"
+}

First observedv1.3.1Jul 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds useful non-annotation context: the confirmation requirement, the backing RemoteControl method, and the authentication expectation that no session key should be provided.

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 short sentences, front-loaded with the action and required confirmation, followed by implementation and authentication notes. Every sentence earns its place and nothing is padded.

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?

The definition is complete enough to invoke safely: it identifies the destructive action, requires explicit confirmation, notes authentication expectations, and an output schema exists so return values need not be described. It could add more about downstream effects of deleting a quota, but that is a minor gap.

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 description coverage is 100%, so the schema already documents quota_id, response_format, and confirm_destructive_action. The description adds no parameter meaning beyond what is in the schema, so the baseline of 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?

States a specific verb and resource: 'Delete a survey quota.' This clearly distinguishes the tool from sibling quota operations such as list_quotas, add_quota, get_quota_properties, and set_quota_properties.

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 states a required precondition ('Requires confirm_destructive_action=true'), which helps invocation, but it does not explicitly say when to use this tool versus alternatives like set_quota_properties or list_quotas. Usage is implied by the destructive delete verb.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server