Skip to main content
Glama

learnjcu_list_courses

Read-only

Lists enrolled LearnJCU courses and modules, most recently accessed first, to help you find a course or get its ID for other actions. Filter by course code or name and include past courses.

Instructions

List the modules/courses you are enrolled in on LearnJCU, most recently accessed first. Use when the user asks about their courses or modules, or you need a course id for another LearnJCU tool.

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": "learnjcu_list_courses"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoFilter by text in the course code or name, e.g. "BU2001"
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.
includeUnavailableNoInclude hidden or past courses (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavior beyond that: the default result ordering and, via the 'hidden or past courses' framing of includeUnavailable, the fact that unavailable courses are excluded by default. It says nothing about result size, pagination, or what fields a course entry carries.

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?

Two sentences, both earning their place: the first covers what is returned and in what order, the second covers when to reach for it. Scope and ordering are front-loaded before the usage clause.

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?

For a zero-required-parameter read-only list tool with no output schema and full annotation coverage, the definition supplies what an agent needs: scope, ordering, default exclusion of hidden/past courses, and downstream purpose. Return shape and result volume are left unstated, which is a minor gap given the absence of an output schema.

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 all three parameters are already documented in the schema, including the search example and the account-selection prerequisite. The description adds no parameter-level detail beyond what the schema provides, so the baseline 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?

States a specific verb (List) and resource (modules/courses you are enrolled in on LearnJCU) plus the ordering rule (most recently accessed first). The resource is clearly distinct from sibling list tools such as learnjcu_list_contents, learnjcu_list_announcements, and learnjcu_list_submissions.

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?

Explicitly names two triggers: the user asking about courses/modules, and needing a course id to feed another LearnJCU tool. That second clause gives real routing value toward learnjcu_list_contents and similar tools. No when-not guidance or named alternative for a different scope, so it stops 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.