Skip to main content
Glama

learnjcu_list_contents

Read-only

List items in a course outline; omit content ID for the top level or pass a folder/learning module ID to view children, helping users find assignments and other course items.

Instructions

List items in a course outline. Omit contentId for the top level; pass a folder/learning module id to list its children. Use when the user asks what is in a course, or to find an assignment or other item in it.

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": {
      "courseId": "<courseId>"
    },
    "name": "learnjcu_list_contents"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.
courseIdYesCourse primary id like "_123456_1" (from learnjcu_list_courses), a subject code like "BU2001", or the full course code
contentIdNoFolder id like "_987654_1"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

readOnlyHint=true and openWorldHint=true already declare this is a safe, external read, so the description needn't repeat that. It does add genuinely behavioral detail about the top-level versus child traversal rule, which is not derivable from annotations. It says nothing about pagination, result ordering, or how deep the hierarchy goes — gaps that matter for a listing tool over an external system.

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?

Three short sentences in strict priority order: what it does, how to traverse, when to reach for it. No filler, no restatement of the tool name, and the key optionality rule is stated before the usage trigger.

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?

With no output schema and a simple three-parameter surface, the definition covers the decisions an agent must make: when to call, whether to supply contentId, and which account to target. The remaining omission — what a returned "item" looks like (type, title, id fields) — would help the agent chain into get_content or submit, but is not blocking.

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?

Schema coverage is 100%, so baseline is 3, but the description earns an upgrade: it explains that contentId is optional-and-omitted for top level and that passing a folder/module id returns that node's children — semantics the schema's bare "Folder id like \"_987654_1\"" does not convey. It also implicitly deprioritizes the account parameter, though without restating the schema's guidance there.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: "List items in a course outline." An agent can immediately tell this is a hierarchical listing tool. It does not, however, distinguish itself from learnjcu_get_content, which by name suggests fetching a single item's content — a one-clause differentiation would have earned a 5.

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?

"Use when the user asks what is in a course, or to find an assignment or other item in it" gives a concrete trigger condition tied to user intent. Combined with "Omit contentId for the top level; pass a folder/learning module id to list its children," this effectively explains traversal strategy. No explicit exclusion against sibling tools like get_content, hence not a 5.

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