Skip to main content
Glama

Remind survey participants

limesurvey_remind_participants

Send reminder emails to selected or eligible participants. Requires confirm_send_email=true.

Instructions

Send reminder emails to selected or eligible participants. Requires confirm_send_email=true.

Calls LimeSurvey RemoteControl method remind_participants. 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>",
      "confirm_send_email": "<confirm_send_email>"
    },
    "name": "limesurvey_remind_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_idYesNumeric LimeSurvey survey ID.
token_idsNoParticipant row IDs, or false for eligible participants.
response_formatNoOutput format. JSON preserves the complete structured result; Markdown is optimized for reading.json
continue_on_errorNoContinue after individual email errors.
maximum_remindersNoMaximum reminders per participant.
confirm_send_emailYesRequired acknowledgement that email may be sent to participants.
minimum_days_betweenNoMinimum days since the previous reminder.

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 cover the safety profile (non-read-only, non-idempotent, open-world), and the description adds genuinely useful auth context: it names the RemoteControl method and states that a configured service account is used and no session key should be supplied. It stops short of describing recipient side effects such as how reminder counts are tracked or what happens on partial failures (continue_on_error).

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 sentences, no filler, with the action and the mandatory acknowledgement front-loaded before the auth mechanics. Every clause carries information an agent needs.

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 and annotations covering safety, the description need not explain return values. It adequately covers purpose, confirmation requirement, and auth model, though a note on interaction with sibling email tools would close the remaining 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 the baseline is 3. The description only restates the confirm_send_email requirement already encoded as const: true in the schema and adds no semantics for token_ids, maximum_reminders, or minimum_days_between.

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 ('Send reminder emails to ... participants') with explicit scope ('selected or eligible'). It is distinguishable from sibling tools like invite_participants and mail_registered_participants by the 'reminder' framing, though it does not name them to sharpen the boundary.

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?

Gives one hard prerequisite (confirm_send_email=true) but offers no guidance on when to prefer this over limesurvey_invite_participants or limesurvey_mail_registered_participants, even though those siblings overlap heavily. Usage is implied by the tool's purpose rather than stated.

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