Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

copy_survey

Duplicate an existing LimeSurvey survey to create a new version with a different name, saving time on survey setup.

Instructions

Copy a LimeSurvey survey.

Args:
    sid: The source survey ID.
    new_name: The name for the new survey.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes
new_nameYes

Implementation Reference

  • main.py:379-389 (handler)
    The handler function for the copy_survey tool. It creates a LimeSurvey client using get_client() and calls client.copy_survey(sid, new_name) to copy the survey and return the new survey ID. The @mcp.tool() decorator also serves as the registration.
    @mcp.tool()
    def copy_survey(sid: int, new_name: str) -> int:
        """Copy a LimeSurvey survey.
    
        Args:
            sid: The source survey ID.
            new_name: The name for the new survey.
        """
        with get_client() as client:
            return client.copy_survey(sid, new_name)
  • main.py:15-20 (helper)
    Helper function to create and return a citric Client instance using environment variables for authentication.
    def get_client() -> Client:
        return Client(
            url=os.getenv("LIMESURVEY_URL"),
            username=os.getenv("LIMESURVEY_USERNAME"),
            password=os.getenv("LIMESURVEY_PASSWORD"),
        )
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the action ('Copy') but doesn't disclose what gets copied (structure, settings, data?), permissions required, whether it's idempotent, or what the new survey's initial state is (e.g., active/inactive).

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

Conciseness5/5

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

The description is extremely concise and well-structured: a clear purpose statement followed by brief parameter explanations. Every sentence earns its place with no redundant or vague language.

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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'copy' entails (full/partial duplication), success/failure behaviors, return values, or error conditions—critical gaps for safe tool invocation.

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

Parameters4/5

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

The description adds meaningful context for both parameters: 'sid' is explained as 'source survey ID' and 'new_name' as 'name for the new survey'. With 0% schema description coverage, this compensates well by clarifying parameter roles beyond just their names and types.

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 verb ('Copy') and resource ('LimeSurvey survey'), making the purpose immediately understandable. It distinguishes itself from siblings like 'add_survey' (create new) and 'import_survey' (import from external source), though it doesn't explicitly mention these distinctions.

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. It doesn't mention prerequisites (e.g., needing an existing survey), exclusions, or compare with similar tools like 'import_survey' or 'add_survey' for different creation scenarios.

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