LearningSuite MCP Server

learningsuite_create_group

Create a new group in LearningSuite by specifying a group name and optional description. Use this tool to set up groups for managing members and courses.

Instructions

Create a new 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": {
      "name": "<name>"
    },
    "name": "learningsuite_create_group"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Group name
`description`	No	Group description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.8/5.0

Behavior2/5

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

Annotations are not provided, so the description is the sole source of behavioral disclosure. It only states that a group is created, but does not explain side effects, required permissions, return values, or whether the operation is reversible. 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.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (five words) and front-loaded, but the brevity reflects under-specification rather than effective communication. It merely restates the tool name and does not provide any useful additional information, so it does not fully 'earn its place'.

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?

Given there are no annotations, no output schema, and the description is only five words, the agent lacks critical context about group creation semantics, authentication needs, success/failure behavior, and return data. This is inadequate for a create operation.

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 already provides full coverage for both parameters (name and description), so the description does not need to compensate. The description itself adds no meaning beyond what the schema states, warranting the baseline score of 3.

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?

The description 'Create a new group' clearly specifies the action (create) and the resource (group), making it distinct from sibling tools like create_member or create_hub. However, it is essentially a restatement of the tool name and provides no additional context about what a group is or what creating it entails, so it does not fully differentiate itself beyond the resource name.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, use cases, or exclusions that would help an agent decide between this and other create operations such as create_member or create_hub.

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

Deploy Server