LearningSuite MCP Server

learningsuite_remove_member_from_bundles

Remove a member from one or more bundles by supplying the member ID and an array of bundle IDs.

Instructions

Remove a member from one or more bundles

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": {
      "memberId": "<memberId>",
      "bundleIds": "<bundleIds>"
    },
    "name": "learningsuite_remove_member_from_bundles"
  }
}

Input Schema

Name	Required	Description	Default
`memberId`	Yes	Member ID
`bundleIds`	Yes	Array of bundle IDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.5/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 full responsibility for behavioral disclosure. It only states the action without mentioning side effects, idempotency, permission requirements, or what happens on partial failure. This is a significant gap for a mutation tool.

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 concise sentence with no wasted words. It clearly conveys the core action without unnecessary elaboration.

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 2-parameter mutation tool with no output schema and no annotations, the description covers the basic action and parameters. However, it lacks behavioral details like reversibility or idempotency, making it adequate but not complete.

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%, with both parameters (memberId, bundleIds) having descriptions in the schema. The description adds no additional parameter detail beyond what the schema already provides, so baseline 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 'Remove a member from one or more bundles' uses a specific verb (Remove) and clearly identifies the resource (member) and target (bundles). It distinguishes itself from sibling tools like add_member_to_bundles and remove_member_from_courses by precisely stating the action.

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 implies the tool is for removing members from bundles but provides no explicit guidance on when to use it over alternatives, no prerequisites, and no exclusions. The usage is inferred from the action, but no alternatives or context are mentioned.

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

Deploy Server