Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

by edgarrmondragon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_group

Remove a question group from a LimeSurvey survey by specifying the survey ID and group ID to manage survey structure.

Instructions

Delete a group from a LimeSurvey survey.

Args:
    sid: The survey ID.
    gid: The group ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sidYes
gidYes

Implementation Reference

  • main.py:449-459 (handler)
    The main handler function for the 'delete_group' tool. It is decorated with @mcp.tool() which registers it in FastMCP with the name 'delete_group' based on the function name. The function deletes a question group from a survey by calling the underlying LimeSurvey client's delete_group method.
    @mcp.tool()
def delete_group(sid: int, gid: int) -> bool:
    """Delete a group from a LimeSurvey survey.

    Args:
        sid: The survey ID.
        gid: The group ID.
    """
    with get_client() as client:
        return client.delete_group(sid, gid)

Tool Definition Quality

B3.1/5.0
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 only mentions the action 'Delete' without disclosing behavioral traits like whether this is irreversible, requires specific permissions, affects related data, or returns confirmation. This is inadequate for a destructive operation.

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 efficiently structured with a brief purpose statement followed by parameter explanations, using minimal words without redundancy. Every sentence adds value, making it easy to parse quickly.

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 destructive tool with no annotations and no output schema, the description is incomplete—it lacks crucial information about consequences, permissions, return values, or error handling. Given the complexity and risk, more context is needed.

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?

Schema description coverage is 0%, but the description explicitly documents both parameters ('sid' as survey ID and 'gid' as group ID) with clear semantics, compensating fully for the schema gap. It doesn't provide format details but gives essential meaning.

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 ('Delete') and target resource ('a group from a LimeSurvey survey'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'delete_survey' or 'delete_question' beyond mentioning 'group' specifically.

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 like 'delete_survey' or 'delete_question', nor any prerequisites or warnings about irreversible deletion. The description only states what it does without context for 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