Skip to main content
Glama

Get quota properties

limesurvey_get_quota_properties
Read-onlyIdempotent

Read selected quota properties.

Instructions

Read selected quota properties.

Calls LimeSurvey RemoteControl method get_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>"
    },
    "name": "limesurvey_get_quota_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLimeSurvey language code; null uses the survey default.
quota_idYesNumeric quota ID.
propertiesNoProperties to return for the quota; null returns all available properties.
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

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds real behavioral context beyond that: it is a passthrough to the RemoteControl method and, notably, that auth uses the configured service account and no session key should be supplied — a concrete invocation requirement an agent would otherwise get wrong.

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, purpose first, then the method/auth note — no filler and properly front-loaded. Slightly terse rather than maximally information-dense, but nothing is wasted.

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

Completeness4/5

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

With an output schema present, return values need not be described, and the schema fully documents inputs. The description supplies purpose and the key auth constraint, leaving it complete enough for correct invocation; only cross-sibling routing is missing.

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%, with quota_id, language, properties and response_format all documented in the schema, so the schema carries the semantics. The description adds nothing about parameters, which is the correct baseline of 3 when the schema already does the heavy lifting.

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 and resource ("Read selected quota properties") and names the underlying RemoteControl method, which is enough to distinguish it from mutation siblings like set_quota_properties, add_quota, and delete_quota. It does not explicitly contrast itself with read siblings such as list_quotas or get_survey_properties, so it falls short of a 5.

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?

There is no when-to-use guidance, no mention of when to prefer list_quotas over this, and no stated prerequisites. Usage is only inferable from the verb 'Read', which is the minimum for implied understanding rather than clear routing.

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