LearningSuite MCP Server

learningsuite_send_push_notifications

Send push notifications to specific users or groups via custom app, with customizable title, body, link, and image to notify recipients.

Instructions

Send push notifications to users (requires custom app)

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": {
      "linkUrl": "<linkUrl>"
    },
    "name": "learningsuite_send_push_notifications"
  }
}

Input Schema

Name	Required	Description
`body`	No	Notification body text
`title`	No	Notification title
`linkUrl`	Yes	Link URL when tapped
`userIds`	No	Array of user IDs
`groupIds`	No	Array of group IDs
`publicImageUrl`	No	Public image URL for notification

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?

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only mentions the custom app requirement and does not explain side effects, permission needs, delivery behavior, or what happens when no user/group IDs are specified.

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?

The description is a single sentence with no redundant wording, front-loading the primary action and constraint effectively. It is appropriately concise for the information it contains.

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

Completeness2/5

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

This is a side-effectful mutation tool with six parameters, no annotations, and no output schema. The description is too minimal to cover essential context such as target selection behavior, required permissions, or expected outcomes, leaving significant gaps for an AI agent.

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 parameters are already described in the schema. The tool description adds no additional parameter meaning beyond what the schema provides, matching the baseline for high schema coverage.

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 clearly states the tool sends push notifications to users, using a specific verb and resource. It distinguishes itself from sibling tools as the only one for this purpose, and adds a relevant constraint about requiring a custom app.

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?

No guidance is provided on when to use this tool versus alternatives, and no exclusions or alternative tools are mentioned. The only context is the prerequisite 'requires custom app', which is not a usage recommendation.

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

Deploy Server