Skip to main content
Glama

List surveys

limesurvey_list_surveys
Read-onlyIdempotent

List surveys visible to a user, optionally filtered by survey group.

Instructions

List surveys visible to a user, optionally filtered by survey group.

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "limesurvey_list_surveys"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameNoOptional administration username; null uses the current service account.
response_formatNoOutput format. JSON preserves the complete structured result; Markdown is optimized for reading.json
survey_group_idNoOptional survey-group ID.

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.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely useful behavioral context beyond that: it states that the call hits LimeSurvey RemoteControl method `list_surveys` and that authentication uses the configured service account with no session key required, which pre-empts a real misuse pattern given the get_session_key/release_session_key siblings.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two short sentences, front-loaded with the purpose and filter, followed by the one piece of context an agent cannot get from structured fields (the auth model). 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 annotations cover the safety profile. The description supplies purpose, filter, and auth behavior, so an agent has enough to invoke it correctly; only the relationship to the sibling search tool (find_surveys) is left unaddressed.

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 three parameters (username, response_format, survey_group_id) are already documented in the schema, and the description's survey-group mention duplicates that. The service-account note implicitly clarifies the username parameter's default behavior, but no additional syntax or format detail is added over the schema. Baseline 3 is appropriate.

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 ('List surveys') plus the scope ('visible to a user') and an optional narrowing filter ('filtered by survey group'). It is clearly distinct from mutation siblings like add_survey or delete_survey, though it never names the closest read alternative, limesurvey_find_surveys, leaving that differentiation to inference.

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

Usage Guidelines3/5

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

The description gives one clear usage condition (optionally filter by survey group) and an operational instruction about authentication, but it offers no when-to-use/when-not guidance and does not point to limesurvey_find_surveys for searching versus listing. Usage is implied rather than directed.

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