Skip to main content
Glama

Create quota

limesurvey_add_quota

Create a quota with minimum details.

Instructions

Create a quota with minimum details.

Calls LimeSurvey RemoteControl method add_quota. 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": {
      "survey_id": "<survey_id>",
      "name": "<name>",
      "limit": "<limit>"
    },
    "name": "limesurvey_add_quota"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoQuota redirect URL.
nameYesQuota name.
limitYesMaximum responses allowed.
actionNoQuota action.
activeNoActivate the quota immediately.
messageNoQuota message.
survey_idYesNumeric LimeSurvey survey ID.
autoload_urlNoAutomatically load the quota URL.
response_formatNoOutput format. JSON preserves the complete structured result; Markdown is optimized for reading.json
url_descriptionNoQuota URL label.

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

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so the mutation profile is covered. The description adds genuinely useful context the annotations do not: authentication uses the configured service account and no session key should be supplied. It stops short of describing persistence or side effects on existing surveys.

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?

Two short sentences with the action front-loaded and the auth note clearly separated. No filler, though the second sentence could be slightly tighter.

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

Completeness3/5

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

An output schema exists so return values need no explanation, and the auth prerequisite is covered. For a 10-parameter mutation tool, however, the absence of any when-to-use routing relative to the other quota tools leaves a meaningful gap.

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?

Schema description coverage is 100%, so all 10 parameters are already documented in the schema. The phrase 'with minimum details' hints that only the 3 required fields are needed, but adds little semantic detail beyond what the schema provides. Baseline 3 applies.

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?

States a specific verb+resource ('Create a quota') and even names the underlying RemoteControl method, so an agent knows exactly what it does. It does not explicitly differentiate from siblings like set_quota_properties or list_quotas, but the create-vs-modify distinction is inferable from the verb.

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?

The description says only 'with minimum details' and gives no guidance on when to use this versus set_quota_properties, get_quota_properties, or list_quotas. There are no exclusions or alternative routing, leaving usage to inference.

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