LimeSurvey MCP Server

Get survey summary

limesurvey_get_summary

Read-onlyIdempotent

Instructions

Read response and participant summary counters. The answer "No available data" is not a call error: for token_* statistics it means the survey has no participant table (no participant statistics; error hint_code NO_PARTICIPANT_TABLE; access is decided by access_mode, check limesurvey_get_participant_table_status), for response statistics it means the survey has no response table: never activated or deactivated (hint_code NO_RESPONSE_TABLE). With statistic=all only the available parts are returned.

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

Input Schema

Name	Required	Description	Default
`statistic`	No	Summary statistic to return.
`survey_id`	Yes	Numeric LimeSurvey survey ID.
`response_format`	No	Output format. JSON preserves the complete structured result; Markdown is optimized for reading.	json

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.3/5.0

Behavior5/5

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

Annotations already establish read-only/idempotent/non-destructive, and the description goes well beyond them: it explains that 'No available data' is a normal result rather than a call error, gives the hint codes NO_PARTICIPANT_TABLE and NO_RESPONSE_TABLE with their causes, and notes that statistic=all returns only the available parts. It also states that the configured service account is used and no session key should be supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence and the dense error-semantics passage that follows is directly load-bearing for interpreting results. It is somewhat wordy, but no sentence is filler.

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?

An output schema exists, so return shape need not be described. For a 3-parameter read tool with full schema coverage, the description covers the main pitfall (the 'No available data' response), the auth model, and the access_mode dependency — nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both enums are documented, so the baseline is 3. The description adds meaning on top of the enum list by explaining the semantic split between the token_* statistics and the response statistics, which helps the agent choose a value rather than just see the options.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Read response and participant summary counters') and names the underlying RemoteControl method `get_summary`, which is enough to distinguish it from export_statistics or export_timeline. It does not explicitly contrast itself with those siblings, so it stops short of a 5.

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?

Gives real context for when results are meaningful: it distinguishes token_* statistics (needs a participant table) from response statistics (needs a response table), and points the agent to limesurvey_get_participant_table_status and access_mode when participant stats are in question. It does not state when to prefer this over export_statistics, so no exclusions are covered.

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

Deploy Server