Skip to main content
Glama
Sign In
LearningSuite MCP Server

LearningSuite MCP Server

by fabienbutz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

learningsuite_list_hubs

Retrieve the full list of published hubs from LearningSuite. Access hub information for courses, groups, and community management.

Instructions

Get all published hubs

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "learningsuite_list_hubs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the burden, but it only states the action without disclosing details like authentication requirements, potential pagination, or the exact nature of 'published'. However, the word 'published' does add a filtering behavior, which is minimal but useful.

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 clear sentence with no redundant or irrelevant content. It is highly concise and front-loaded with the essential action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity (0 parameters, no output schema, no annotations), the description sufficiently conveys the tool's purpose and scope. It does not mention potential limitations like large data handling, but for a simple list operation, this is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, making parameter semantics trivial. The description adds no parameter details because none are needed, and the schema coverage is complete by default.

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 "Get all published hubs" uses a specific verb ('Get') and resource ('published hubs'), clearly indicating the tool's function. It distinguishes from sibling tools like 'learningsuite_list_hub_templates' and 'learningsuite_create_hub' by specifying the resource scope.

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 about when to use this tool versus alternatives. There is no mention of prerequisites, alternatives, or exclusions, leaving the agent without contextual selection cues.

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

Deploy Server

Other Tools