Skip to main content
Glama
Sign In
LearningSuite MCP Server

LearningSuite MCP Server

by fabienbutz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

learningsuite_get_bundle_members

Retrieve members of a bundle along with their access info. Provide a bundleId, and optionally set limit and offset for paginated results.

Instructions

Get members of a bundle with access info

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": {
      "bundleId": "<bundleId>"
    },
    "name": "learningsuite_get_bundle_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum to return (max 200)
offsetNoOffset for pagination
bundleIdYesBundle ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/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. The verb 'Get' implies a read-only operation, and 'with access info' hints at the return content. However, it does not explain pagination behavior, return format, or any potential side effects, leaving significant behavioral details undisclosed.

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, front-loaded sentence that efficiently conveys the action and key detail. Every word earns its place, with no redundancy or unnecessary prose.

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

Completeness3/5

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

For a simple list/gamut tool, the description adequately states the purpose and mentions 'access info' as a return aspect. However, without an output schema or annotation, it lacks details on the exact structure of the returned members and access info, and the pagination behavior is only implied by the parameters.

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 already provides 100% coverage, describing each parameter (bundleId, limit, offset). The description adds no extra meaning to these parameters, so it does not exceed the baseline of relying on the schema.

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 states the action (Get), the resource (members of a bundle), and adds a specific detail (with access info). This distinguishes it from sibling tools like get_member_bundles, which retrieves bundles for a member, making the purpose unambiguous.

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 context of when to use the tool is clear: when you need members of a bundle. It doesn't explicitly name alternatives or exclusions, but the straightforward phrasing implies the intended use. The tool's name also aligns with the description, reinforcing its role without confusion.

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