LearningSuite MCP Server

learningsuite_add_courses_to_group

Assign multiple courses to a group by providing the group ID and an array of course IDs.

Instructions

Add courses to a group

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": {
      "groupId": "<groupId>",
      "courseIds": "<courseIds>"
    },
    "name": "learningsuite_add_courses_to_group"
  }
}

Input Schema

Name	Required	Description	Default
`groupId`	Yes	Group ID
`courseIds`	Yes	Array of course IDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention whether courses are appended or replace existing ones, whether group validation is performed, permission requirements, or error handling. This leaves significant ambiguity for a mutation operation.

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 extremely concise and front-loaded, with no filler. However, it is so minimal that it essentially restates the tool name, offering little value beyond brevity.

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?

The tool has only two simple parameters and no output schema, so the description could be minimal. Yet it still lacks important context about whether the operation is additive or replacement, and how it behaves if some course IDs are invalid. This leaves the agent under-informed for correct invocation.

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 'groupId' and 'courseIds' fully described. The description adds no additional meaning beyond the schema, so the baseline score 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 'Add courses to a group' is a specific verb+resource statement that clearly indicates the operation. It distinguishes from sibling tools like 'learningsuite_remove_courses_from_group' and 'learningsuite_add_bundles_to_group' by explicitly mentioning 'courses' and 'group'.

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 such as adding members to courses or adding bundles to groups. There is no context about prerequisites, typical scenarios, or exclusions.

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

Deploy Server