LearningSuite MCP Server

learningsuite_trigger_popup

Trigger a specific popup for a member by supplying popup ID and member ID. Deliver targeted messages to individual members in LearningSuite.

Instructions

Trigger a popup for a member

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": {
      "popupId": "<popupId>",
      "memberId": "<memberId>"
    },
    "name": "learningsuite_trigger_popup"
  }
}

Input Schema

Name	Required	Description	Default
`popupId`	Yes	Popup ID
`memberId`	Yes	Member ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description does not mention any side effects (e.g., whether the popup is displayed to the member, triggers a notification, or requires specific permissions), nor does it describe return values or failure modes. It is a minimal statement of action without behavioral nuance.

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?

The description is a single, clear sentence that communicates the core action without waste. It is appropriately sized for a simple tool, though it could have included more guidance without becoming verbose.

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?

For a simple tool with two fully documented parameters and no output schema, the description covers the essential purpose. However, it lacks context about when to use this tool versus others and lacks any note on expected outcomes or side effects, making it marginally complete but not fully informative.

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?

The input schema has 100% description coverage for its two parameters ('Popup ID' and 'Member ID'). The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Trigger a popup for a member' uses a specific verb ('Trigger') with a clear resource ('popup') and target ('member'). It distinguishes from sibling tools like 'list_popups' and 'remove_popup_trigger' by indicating the specific action of triggering, not listing or removing.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or scenarios where this tool should be preferred over others like 'get_popup' or 'remove_popup_trigger'. The agent is left to infer usage solely from the tool's name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server