Skip to main content
Glama

Set quota properties

limesurvey_set_quota_properties

Update quota properties. Writable fields: name, qlimit, action, active, autoload_url. NOT writable through RemoteControl (the call is rejected before any request is sent): id, sid, limit, quotals_message, quotals_url, quotals_urldescrip.

Instructions

Update quota properties. Writable fields: name, qlimit, action, active, autoload_url. NOT writable through RemoteControl (the call is rejected before any request is sent): id, sid, limit, quotals_message, quotals_url, quotals_urldescrip. Localized quota texts (message, URL, URL description) can only be edited in the LimeSurvey admin UI. Unknown keys are ignored silently by LimeSurvey; the server reports them in warnings. Keys LimeSurvey does not report back are returned in warnings. Verified against the LimeSurvey 6.17.11 source; older releases may differ.

Calls LimeSurvey RemoteControl method set_quota_properties. Authentication uses the configured service account; do not provide a session key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "quota_id": "<quota_id>",
      "data": "<data>"
    },
    "name": "limesurvey_set_quota_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesQuota properties to update.
quota_idYesNumeric quota ID.
response_formatNoOutput format. JSON preserves the complete structured result; Markdown is optimized for reading.json

Output Schema

NameRequiredDescriptionDefault
methodYes
resultYes
warningsNo
truncatedNo
truncation_messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • addedOutput schema / properties / warnings
      Added value: +{
      +  "items": {
      +    "$ref": "#/definitions/__schema0"
      +  },
      +  "type": "array"
      +}
  2. First observedv1.3.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations (which only flag non-read-only, non-idempotent, open-world, non-destructive), the description discloses that unknown keys are ignored silently, that rejected calls fail before any request is sent, that unreported keys come back in warnings, and that auth uses the configured service account with no session key. It also pins the behavior to a verified LimeSurvey version. This is unusually rich disclosure 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?

Front-loaded with the action and the writable/not-writable split before any meta detail, and no sentence is pure filler. The field lists are dense and the trailing RemoteControl/version sentences are low-priority, but each carries operational value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return values, and it covers everything else an agent needs: the writable key set, the rejected keys, silent-ignore behavior, warning reporting, auth model, and version scope. Nothing material to a correct invocation is missing.

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

Parameters5/5

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

Although the schema covers all three parameters, the `data` object is an untyped anyOf blob with no field names; the description supplies the missing semantics by whitelisting writable keys (name, qlimit, action, active, autoload_url) and blacklisting the rejected ones. That meaning exists nowhere in the schema and is essential to calling the tool correctly.

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

Purpose5/5

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

States a specific verb+resource ('Update quota properties') and immediately enumerates the writable fields, which pins down exactly which slice of quota data this tool mutates versus reading tools like limesurvey_get_quota_properties. An agent can distinguish it from the many sibling set_*_properties tools by the 'quota' resource alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear when-not guidance: localized quota texts (message/URL/URL description) can only be edited in the admin UI, and a set of keys is rejected outright. It does not, however, name the read-side alternative (limesurvey_get_quota_properties) or state prerequisites such as survey activation state, so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools