Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

by edgarrmondragon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

delete_question

Remove a question from a LimeSurvey survey by specifying its question ID to manage survey content and structure.

Instructions

Delete a question from a LimeSurvey survey.

Args:
    qid: The question ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qidYes

Implementation Reference

  • main.py:486-495 (handler)
    The handler function for the 'delete_question' MCP tool. It is decorated with @mcp.tool() for registration and schema inference from signature/docstring. Executes by obtaining a client context and calling client.delete_question(qid).
    @mcp.tool()
def delete_question(qid: int) -> bool:
    """Delete a question from a LimeSurvey survey.

    Args:
        qid: The question ID.
    """
    with get_client() as client:
        return client.delete_question(qid)

Tool Definition Quality

C2.9/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 for behavioral disclosure. It states the action ('Delete') but doesn't mention critical details like whether this is reversible, what permissions are required, if it affects related data, or what the response looks like. This is a significant gap 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.

Conciseness4/5

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

The description is appropriately concise with two sentences: one stating the purpose and another documenting the parameter. It's front-loaded with the main action, though the parameter documentation could be integrated more smoothly.

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 doesn't address behavioral aspects like irreversibility, error conditions, or response format, leaving the agent with insufficient context for safe and effective use.

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

Parameters3/5

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

The description includes an Args section that documents the single parameter (qid) with a brief explanation ('The question ID'), but schema description coverage is 0%. This adds minimal value beyond the schema's type information, meeting the baseline for a tool with one parameter.

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 ('Delete') and resource ('a question from a LimeSurvey survey'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like delete_group or delete_survey, which target different resources in the same system.

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 delete_survey or delete_group, nor are any prerequisites or exclusions mentioned. The description only states what it does, not when it's appropriate.

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