LearningSuite MCP Server

learningsuite_create_hub

Create a hub from a template by specifying its name, template ID, and optional variables. Streamline hub setup by reusing predefined structures.

Instructions

Create a new hub from a template

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>",
      "hubTemplateId": "<hubTemplateId>"
    },
    "name": "learningsuite_create_hub"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Hub name
`variables`	No	Template variables
`hubTemplateId`	Yes	Hub template 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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'create' without mentioning side effects, required permissions, failure modes, or what the response contains. For a mutating operation, this is a notable gap.

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 that front-loads the action and object without any filler. It communicates the core purpose efficiently.

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 the lack of annotations, output schema, and the mutating nature of the tool, the description is insufficiently complete. It does not explain the return value, required preparation steps, or the role of template variables, leaving the agent without crucial context 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 coverage is 100%, with all three parameters having descriptions, so the baseline is 3. The tool description adds no extra semantic detail beyond the schema; it does not clarify how to structure the 'variables' object or where 'hubTemplateId' comes from, but the schema already provides basic meaning.

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 uses a specific verb+resource ('Create a new hub') and adds 'from a template', which clearly differentiates this tool from other create tools like creating groups, members, or lessons. The purpose is immediately unambiguous.

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 offers no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as listing hub templates or retrieving template variables first. The phrase 'from a template' implies a template ID is needed, but it does not instruct the agent on how to obtain or validate it.

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

Deploy Server