LearningSuite MCP Server

learningsuite_remove_hub_accesses

Remove hub access for members, groups, or bundles by specifying the hub ID and target IDs.

Instructions

Remove access from 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_remove_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

B3.4/5.0

Behavior2/5

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

No annotations are provided, and the description is a simple statement of intent. It does not disclose any behavioral details such as whether the removal is reversible, how multiple entity types are handled in one call, or what happens if invalid IDs are passed. This is insufficient 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 that front-loads the action and resource. It contains no redundant words and is appropriately sized for the tool's simplicity.

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 and output schema, the description needs to provide more context. It fails to mention prerequisites, potential side effects, or the relationship between the optional parameters. The tool is a mutation operation, so the absence of behavioral details makes it incomplete.

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 schema provides 100% coverage for parameter descriptions, so the baseline is 3. The tool description merely echoes the parameter types without clarifying how they interact (e.g., whether at least one of the optional arrays is required, or if all can be combined).

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 specifies the action ('Remove access') and the resource ('from a hub'), enumerating the target types ('members, groups, or bundles'). This distinguishes it from the sibling 'learningsuite_add_hub_accesses' and other removal tools.

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 usage for revoking hub access but does not explicitly state when to use this tool over alternatives, nor does it mention exclusions. No comparison with sibling tools like 'learningsuite_add_hub_accesses' is provided.

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

Deploy Server