Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

by edgarrmondragon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

add_response

Submit survey responses to LimeSurvey surveys by providing survey ID and response data for data collection and analysis.

Instructions

Add a response to a LimeSurvey survey.

Args:
    sid: The survey ID.
    response: The response to add.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes
responseYes

Implementation Reference

  • main.py:255-264 (handler)
    The primary handler for the 'add_response' MCP tool. It is registered via the @mcp.tool() decorator and executes the tool logic by using a LimeSurvey client to add the response to the specified survey.
    @mcp.tool()
def add_response(sid: int, response: dict) -> str:
    """Add a response to a LimeSurvey survey.

    Args:
        sid: The survey ID.
        response: The response to add.
    """
    with get_client() as client:
        return client.add_response(sid, response)
  • main.py:15-20 (helper)
    Helper function to create and return a LimeSurvey Client instance, used by the add_response handler.
    def get_client() -> Client:
    return Client(
        url=os.getenv("LIMESURVEY_URL"),
        username=os.getenv("LIMESURVEY_USERNAME"),
        password=os.getenv("LIMESURVEY_PASSWORD"),
    )
  • main.py:255-255 (registration)
    The @mcp.tool() decorator registers the add_response function as an MCP tool.
    @mcp.tool()

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. It states the tool adds a response but doesn't clarify if this is a write operation, what permissions are needed, whether it's idempotent, or what happens on success/failure. For a mutation tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 brief and front-loaded with the core purpose, followed by parameter explanations. It avoids unnecessary fluff, though the parameter section could be more integrated into the flow rather than listed separately.

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 complexity of adding survey responses (a write operation with nested objects), no annotations, no output schema, and low schema coverage, the description is incomplete. It lacks details on error handling, response format, and operational constraints, making it inadequate for safe and effective tool invocation.

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 lists both parameters ('sid' and 'response') and provides basic semantic context (survey ID and response to add). However, with 0% schema description coverage, it doesn't fully compensate by explaining the structure of the response object or format constraints, leaving the agent to infer details from the schema alone.

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 a response') and the target resource ('to a LimeSurvey survey'), which is specific and unambiguous. However, it doesn't distinguish this tool from its sibling 'add_responses' (plural), which could cause confusion about when to use one versus the other.

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 'add_responses' (plural), 'save_responses', or 'update_response'. It also doesn't mention prerequisites such as whether the survey needs to be active or if authentication is required, leaving the agent with insufficient context for proper tool selection.

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