Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

set_group_properties

Configure group settings in LimeSurvey by updating properties like visibility, permissions, or display options for survey question groups.

Instructions

Set LimeSurvey group properties.

Args:
    gid: The group ID.
    properties: The properties to set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gidYes
propertiesYes

Implementation Reference

  • main.py:461-471 (handler)
    The core handler function for the 'set_group_properties' MCP tool. It is decorated with @mcp.tool() which serves as its registration in the FastMCP framework. The function uses type hints and docstring to define input/output schema implicitly, and delegates to the LimeSurvey client library.
    @mcp.tool()
    def set_group_properties(gid: int, properties: dict[str, Any]) -> bool:
        """Set LimeSurvey group properties.
    
        Args:
            gid: The group ID.
            properties: The properties to set.
        """
        with get_client() as client:
            return client.set_group_properties(gid, properties)
  • main.py:15-21 (helper)
    Helper function used by the tool to create an authenticated LimeSurvey Client instance from environment variables.
    def get_client() -> Client:
        return Client(
            url=os.getenv("LIMESURVEY_URL"),
            username=os.getenv("LIMESURVEY_USERNAME"),
            password=os.getenv("LIMESURVEY_PASSWORD"),
        )
  • main.py:461-461 (registration)
    The @mcp.tool() decorator registers the set_group_properties function as an MCP tool.
    @mcp.tool()
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Set' implies a mutation/write operation, but the description doesn't disclose whether this requires specific permissions, whether changes are reversible, what happens to existing properties not mentioned, or what the response looks like. For a mutation tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 two sentences: a purpose statement and a parameter list. It's front-loaded with the main purpose. However, the parameter descriptions are overly minimal and could be more informative without sacrificing conciseness.

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 (mutation tool with nested object parameter), lack of annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what properties can be set, their format, the effect of the operation, or what to expect in return. This leaves significant gaps for an agent to use the tool correctly.

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 two parameters ('gid' and 'properties') but provides minimal semantic information: 'gid: The group ID' is tautological, and 'properties: The properties to set' doesn't explain what properties are available, their format, or constraints. This adds little value beyond the bare parameter names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Set LimeSurvey group properties' which provides a clear verb ('Set') and resource ('group properties'), but it doesn't specify what properties can be set or distinguish this from similar sibling tools like 'set_survey_properties' or 'set_question_properties'. The purpose is understandable but lacks specificity about scope.

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 about when to use this tool versus alternatives. With sibling tools like 'add_group', 'delete_group', and other property-setting tools, the description doesn't indicate whether this is for updating existing groups versus creating new ones, or when to choose this over other property-setting tools.

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