Skip to main content
Glama

learnjcu_calendar

Read-only

List LearnJCU calendar items like course events, due dates, and personal events between two dates; defaults to the next 4 weeks.

Instructions

List LearnJCU calendar items (course events, due dates, personal events) between two dates. Default: next 4 weeks.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoISO date, default now
untilNoISO date, default since + 28 days
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 scope context by naming the three item categories returned and the default time window, but says nothing about result ordering, volume, or authentication requirements.

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 short sentences, resource and scope first, default behavior second. Every clause earns its place with no filler.

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 zero-required-parameter read-only list tool with a fully documented schema and no output schema, the description is adequate but thin: it omits ordering, result size, and how calendar items relate to the dedicated deadlines tool. Nothing is misrepresented, but an agent has open questions before invoking it confidently.

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%, with each of since, until, and account documented in the schema. The description restates the default window (next 4 weeks), which lightly reinforces the since/until defaults, but adds no format or behavior detail beyond the schema — baseline 3.

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 ('List') and resource ('LearnJCU calendar items'), and the parenthetical enumerates what those items include (course events, due dates, personal events). It does not explicitly contrast itself with the closest sibling, learnjcu_upcoming_deadlines, so an agent must still reason about overlap.

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?

The only guidance is the date-range default ('next 4 weeks'); there is no statement of when to prefer this over siblings such as learnjcu_upcoming_deadlines or learnjcu_list_announcements, nor any exclusion or prerequisite. Usage is implied by the name and default range alone.

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