Skip to main content
Glama
edgarrmondragon

LimeSurvey MCP Server

by edgarrmondragon
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

set_quota_properties

Configure survey response limits by modifying quota properties in LimeSurvey to control data collection parameters.

Instructions

Set LimeSurvey quota properties.

Args:
    id: The quota ID.
    properties: The properties to set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
propertiesYes

Implementation Reference

  • main.py:657-666 (handler)
    The MCP tool handler for 'set_quota_properties'. It retrieves a LimeSurvey client and calls set_quota_properties on it to update the quota with the given ID using the provided properties.
    @mcp.tool()
def set_quota_properties(id: int, properties: dict[str, Any]) -> bool:
    """Set LimeSurvey quota properties.

    Args:
        id: The quota ID.
        properties: The properties to set.
    """
    with get_client() as client:
        return client.set_quota_properties(id, properties)

Tool Definition Quality

C2.4/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool performs a 'Set' operation, implying mutation, but doesn't describe permissions required, whether changes are reversible, error conditions, or what happens to unspecified properties. This leaves significant gaps for a mutation tool.

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 brief and front-loaded with the main purpose, followed by a parameter list. It avoids unnecessary words, but the parameter explanations are overly terse and could benefit from more detail without sacrificing efficiency.

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 objects, no annotations, no output schema, and 0% schema coverage), the description is incomplete. It lacks details on behavioral traits, parameter constraints, and expected outcomes, making it inadequate for safe and effective use by an AI agent.

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 parameters 'id' and 'properties' with brief explanations, but 'properties' is described only as 'The properties to set', which is tautological and doesn't clarify what properties are valid, their format, or examples. This adds minimal value beyond the schema.

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 the tool 'Set LimeSurvey quota properties', which provides a clear verb ('Set') and resource ('quota properties'), but it's somewhat vague about what 'properties' specifically means. It doesn't differentiate from sibling tools like 'set_group_properties' or 'set_survey_properties' beyond the resource name.

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. It doesn't mention prerequisites (e.g., needing an existing quota ID), exclusions, or compare it to related tools like 'add_quota' or 'delete_quota' from the sibling list.

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