Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

by edgarrmondragon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

add_participants

Add participants to a LimeSurvey survey by providing survey ID and participant data to populate your study or research.

Instructions

Add participants to a LimeSurvey survey.

Args:
    sid: The survey ID.
    participant_data: The participant data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes
participant_dataYes

Implementation Reference

  • main.py:558-570 (handler)
    The handler function for the 'add_participants' MCP tool. It is decorated with @mcp.tool() for registration and executes the tool logic by adding participants to a LimeSurvey survey using the client.
    @mcp.tool()
def add_participants(
    sid: int, participant_data: list[dict[str, Any]]
) -> list[dict[str, Any]]:
    """Add participants to a LimeSurvey survey.

    Args:
        sid: The survey ID.
        participant_data: The participant data.
    """
    with get_client() as client:
        return client.add_participants(sid, participant_data)

Tool Definition Quality

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions adding participants but fails to disclose critical behavioral traits: whether this requires specific permissions, if it's idempotent, what happens on duplicate entries, rate limits, or the response format. For a mutation tool with zero annotation coverage, this is a significant gap.

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 sized with two sentences: a clear purpose statement and a parameter list. It's front-loaded with the main action, though the parameter explanations are brief and could be more informative without adding bulk.

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 the tool's complexity (a mutation with 2 parameters), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on permissions, error handling, return values, and how it differs from sibling tools, making it inadequate for safe and effective use by an AI agent.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It lists the parameters ('sid' and 'participant_data') but adds minimal meaning beyond the schema—only clarifying that 'sid' is 'The survey ID' and 'participant_data' is 'The participant data', without explaining data format, structure, or examples. This insufficiently compensates for the coverage gap.

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 ('Add participants') and the resource ('to a LimeSurvey survey'), which provides a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'invite_participants' or 'import_cpdb_participants' that also involve participants, missing full sibling differentiation.

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 'invite_participants' or 'import_cpdb_participants', nor does it mention prerequisites such as whether the survey must be active. It only states what the tool does, not when or why to use it.

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