LearningSuite MCP Server

learningsuite_get_member_courses

Retrieve all courses for a member, including access and progress details. Pass the member ID to get a complete list with pagination and date-based access checking.

Instructions

Get all courses for a member with access and progress 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": {
      "memberId": "<memberId>"
    },
    "name": "learningsuite_get_member_courses"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum courses to return
`offset`	No	Offset for pagination
`memberId`	Yes	Member ID
`dateForAccessCheck`	No	Date for access check (ISO format)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations are absent, so the description carries the burden. It adds 'with access and progress info,' which clarifies the returned data beyond just listing courses. However, it does not disclose pagination behavior, ordering, or the effect of dateForAccessCheck, which could be important for accurate invocation.

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 with no redundancy. It efficiently conveys the core purpose and the extra data provided, earning a perfect score for conciseness.

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 read operation with fully schema-documented parameters, the description is adequate but not rich. It mentions access and progress info but omits output structure, pagination defaults, or the meaning of dateForAccessCheck. Given there is no output schema, slightly more detail would improve completeness, but the current description is not severely lacking.

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 schema already documents all parameters. The description adds no additional meaning beyond 'all courses,' and does not elaborate on how limit, offset, or dateForAccessCheck affect results. Thus, the baseline of 3 applies.

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 tool's function: 'Get all courses for a member with access and progress info.' It uses a specific verb and resource, and distinguishes itself from siblings like learningsuite_get_member_course_info (which likely retrieves a single course) and learningsuite_get_course_members (reverse relationship).

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 on when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or comparison with related tools such as get_member_course_info or get_course_members. The description only states what it does, leaving usage entirely implied.

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

Deploy Server