LearningSuite MCP Server

learningsuite_add_hub_accesses

Grant members, groups, or bundles access to a specific hub by providing their IDs.

Instructions

Add access to a hub for members, groups, or 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": {
      "hubId": "<hubId>"
    },
    "name": "learningsuite_add_hub_accesses"
  }
}

Input Schema

Name	Required	Description
`hubId`	Yes	Hub ID
`groupIds`	No	Array of group IDs
`bundleIds`	No	Array of bundle IDs
`memberIds`	No	Array of member IDs

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description alone bears the burden of behavioral disclosure. It does not mention idempotency, whether access is additive or replacing, prerequisites like existence of hubId or entity IDs, or error behavior. 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 sentence with 11 words, front-loaded and directly to the point. Every word earns its place without unnecessary elaboration.

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?

With four parameters and no output schema, the description should explain expected behavior, such as whether at least one of groupIds/bundleIds/memberIds must be provided, whether the operation is immediate, or what the response contains. The description is too sparse to be fully contextual for a tool of this complexity.

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 the baseline is 3. The description adds minimal semantic value by mapping parameters to 'members, groups, or bundles,' but it does not clarify relationships or requirements beyond the property names.

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 identifies the action ('Add access to a hub') and specifies the recipients ('members, groups, or bundles'), using a specific verb and resource combination. This distinguishes it from sibling tools like learningsuite_remove_hub_accesses and other access-granting tools for courses or bundles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context that this tool is for granting hub access to various entity types, implying its use case. However, it lacks explicit when-not-to-use guidance or alternative tool mentions, so it falls short of a 5.

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

Deploy Server