Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

by edgarrmondragon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

add_survey

Create a new survey in LimeSurvey by providing survey data through the MCP server integration.

Instructions

Add a new LimeSurvey survey.

Args:
    survey_data: The survey data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
survey_dataYes

Implementation Reference

  • main.py:368-377 (handler)
    The main handler function for the 'add_survey' MCP tool. It is decorated with @mcp.tool() for registration and executes the logic to add a new survey using the LimeSurvey client by calling client.add_survey with the provided survey_data.
    @mcp.tool()
def add_survey(survey_data: dict[str, Any]) -> int:
    """Add a new LimeSurvey survey.

    Args:
        survey_data: The survey data.
    """
    with get_client() as client:
        return client.add_survey(**survey_data)

Tool Definition Quality

C2.6/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 states this is a creation operation ('Add'), implying mutation, but doesn't disclose behavioral traits like required permissions, whether the survey becomes active immediately, error handling, or what the response contains. This is inadequate for a mutation tool with zero annotation coverage.

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

Conciseness3/5

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

The description is brief and front-loaded with the main purpose, but the 'Args' section is redundant since it repeats what's in the schema without adding semantics. It could be more efficient by integrating parameter details into the main sentence or omitting the redundant listing.

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 no annotations, no output schema, and low schema coverage (0%), the description is incomplete. It doesn't explain what 'survey_data' entails, what happens after creation, or how this differs from sibling tools. For a mutation tool with nested parameters, more context is needed to be fully helpful.

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 only names the parameter ('survey_data') without explaining what it should contain, such as required fields, structure, or examples. This adds minimal value beyond the schema, leaving the parameter largely undocumented.

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') and resource ('a new LimeSurvey survey'), making the purpose understandable. However, it doesn't differentiate from similar tools like 'import_survey' or 'copy_survey', which could also create surveys through different methods.

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?

No guidance is provided on when to use this tool versus alternatives like 'import_survey' or 'copy_survey'. The description lacks context about prerequisites, such as whether authentication or specific permissions are needed, or what distinguishes this from other survey creation methods.

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