Skip to main content
Glama

Email registered participants

limesurvey_mail_registered_participants

Send registration emails to survey participants. Requires confirm_send_email=true.

Instructions

Send registration emails to survey participants. Requires confirm_send_email=true.

Calls LimeSurvey RemoteControl method mail_registered_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_mail_registered_participants"
  }
}

Input Schema

NameRequiredDescriptionDefault
survey_idYesNumeric LimeSurvey survey ID.
response_formatNoOutput format. JSON preserves the complete structured result; Markdown is optimized for reading.json
confirm_send_emailYesRequired acknowledgement that email may be sent to participants.
override_conditionsNoReplacement email conditions as an object or positional condition list.

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 readOnly=false, idempotent=false, destructive=false, so the safety profile is partly covered. The description adds real value beyond them: it discloses that emails are actually sent to participants, names the underlying RemoteControl method, and specifies that auth uses the configured service account with no session key. It stops short of stating failure behavior or per-invocation side effects.

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 that front-load the action and the hard prerequisite, followed by the method/auth note. No filler, and the most decision-relevant fact (requires confirm_send_email=true) comes early.

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 available, return values need not be explained, and the annotations cover the mutation profile. The description covers purpose, prerequisite, and auth, leaving only sibling differentiation and failure/repeat-send behavior 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 the parameters are already documented. The description only restates the confirm_send_email requirement and adds nothing about survey_id semantics or the override_conditions parameter, so the 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 (Send) and resource (registration emails to survey participants), so the action is unambiguous. It does not, however, distinguish itself from close siblings like limesurvey_invite_participants and limesurvey_remind_participants, which all appear to send participant email.

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 prerequisite (confirm_send_email=true), which is genuine usage context. But it offers no when-to-use guidance relative to the obvious alternatives (invite_participants, remind_participants, add_participants), leaving selection between the mail-related tools 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