Skip to main content
Glama

learnjcu_list_announcements

Read-only

List recent announcements for a JCU course, newest first, to quickly review course updates and important notices.

Instructions

List recent announcements for a course, newest first.

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_announcements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 a genuine behavioral fact — results come back newest first — but says nothing about default page size, whether 'recent' is bounded, or what an announcement record contains beyond the title. Adequate, not rich.

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?

One sentence with no filler, and the ordering guarantee is front-loaded so the agent sees it before forming the call. Nothing is padded or repeated from the schema.

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 low-complexity read-only list tool with a 67%-documented schema and no output schema, the definition covers what the call does and how results are ordered. The remaining gap is pagination/limit default behavior, which is minor but real for a 'recent' listing.

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 coverage is 67% and the two documented parameters already explain courseId formats and the account selector, including the pointer to learnjcu_list_accounts. The description adds ordering semantics tied to the limit parameter but never mentions limit, its 1-100 range, or any default, so it does not close the remaining coverage gap.

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?

The description gives a specific verb and resource (list announcements), scopes it to a course, and adds ordering (newest first), which distinguishes it from siblings like learnjcu_list_contents or learnjcu_calendar. It stops short of explicitly naming a contrasting alternative, but the action is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'for a course' signals the courseId-scoped case, and 'recent' hints at a bounded listing. There is no explicit when-to-use, no exclusion of alternatives, and no note on how to choose an account when several are saved beyond what the schema already says.

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