Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

add_responses

Add multiple survey responses to a LimeSurvey survey using the survey ID and response data.

Instructions

Add multiple responses to a LimeSurvey survey.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes
responsesYes

Implementation Reference

  • main.py:267-276 (handler)
    The handler function for the 'add_responses' MCP tool. Decorated with @mcp.tool() for automatic registration and schema inference from type hints and docstring. Executes by creating a LimeSurvey Client and calling its add_responses method.
    @mcp.tool()
    def add_responses(sid: int, responses: list[dict]) -> str:
        """Add multiple responses to a LimeSurvey survey.
    
        Args:
            sid: The survey ID.
            responses: The responses to add.
        """
        with get_client() as client:
            return client.add_responses(sid, responses)
  • main.py:15-20 (helper)
    Helper function to create and return a configured LimeSurvey Client instance, used by the add_responses handler.
    def get_client() -> Client:
        return Client(
            url=os.getenv("LIMESURVEY_URL"),
            username=os.getenv("LIMESURVEY_USERNAME"),
            password=os.getenv("LIMESURVEY_PASSWORD"),
        )
  • main.py:267-267 (registration)
    The @mcp.tool() decorator registers the add_responses function as an MCP tool.
    @mcp.tool()
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 responses but doesn't clarify whether this is a write operation, what permissions are required, if it's idempotent, how errors are handled, or what the output looks like. 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 appropriately concise with three sentences: a clear purpose statement followed by parameter explanations. It's front-loaded with the main action, and each sentence adds necessary information without redundancy. However, the parameter explanations are overly brief given the low schema coverage.

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 write operation with two parameters), lack of annotations, 0% schema description coverage, and no output schema, the description is insufficient. It doesn't address behavioral aspects like side effects, error handling, or return values, nor does it provide adequate parameter semantics or usage guidance, making it incomplete for effective agent use.

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 for undocumented parameters. It lists the two parameters (sid, responses) and briefly describes them ('The survey ID', 'The responses to add'), but this adds minimal semantic value beyond the schema's property names. It doesn't explain the format of responses, what constitutes a valid survey ID, or provide examples, leaving significant gaps.

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 multiple responses') and target resource ('to a LimeSurvey survey'), making the purpose immediately understandable. It distinguishes from the sibling 'add_response' by specifying 'multiple responses' rather than a single response, though it doesn't explicitly contrast with other survey-related tools like 'save_responses' or 'update_response'.

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_response' (for single responses), 'save_responses', or 'update_response'. It mentions the required parameters but offers no context about prerequisites, error conditions, or typical use cases, leaving the agent to infer usage from tool names alone.

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