Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

by edgarrmondragon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_participants

Remove survey participants by specifying their tokens and survey ID to manage participant data in LimeSurvey.

Instructions

Delete participants from a LimeSurvey survey.

Args:
    sid: The survey ID.
    tokens: The participant tokens.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes
tokensYes

Implementation Reference

  • main.py:572-582 (handler)
    The handler function for the 'delete_participants' MCP tool. It is registered with @mcp.tool() decorator and executes the deletion by calling the underlying LimeSurvey client method.
    @mcp.tool()
def delete_participants(sid: int, tokens: list[str]) -> bool:
    """Delete participants from a LimeSurvey survey.

    Args:
        sid: The survey ID.
        tokens: The participant tokens.
    """
    with get_client() as client:
        return client.delete_participants(sid, tokens)

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Delete' implies a destructive operation, it doesn't specify whether this action is reversible, what permissions are required, how errors are handled, or what happens to associated data. For a destructive tool, this is a significant gap in transparency.

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?

The description is appropriately concise with two sentences: one stating the purpose and another listing parameters. It's front-loaded with the main action, though the parameter listing could be integrated more smoothly.

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

Completeness2/5

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

Given this is a destructive tool with no annotations, no output schema, and low parameter semantics coverage, the description is incomplete. It lacks critical context like side effects, return values, error conditions, or usage examples, which are essential for safe operation.

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 description adds minimal semantics beyond the input schema by naming the parameters ('sid' as survey ID and 'tokens' as participant tokens). However, with 0% schema description coverage, it doesn't fully compensate—it doesn't explain token format, sid constraints, or array handling. Baseline 3 is appropriate given the schema does the structural heavy lifting.

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?

The description clearly states the action ('Delete participants') and the resource ('from a LimeSurvey survey'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_survey' or 'delete_response' beyond mentioning participants specifically, which is why it's not a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'delete_response' or 'delete_survey', nor does it mention prerequisites or constraints. It simply states what the tool does without contextual usage information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/edgarrmondragon/limesurvey-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server