Skip to main content
Glama

studentfirst_overview

Read-only

View your next 8 days of StudentFirst classes with times, rooms, campus and overall attendance against the 90% minimum, plus sessions attended per class at JCU Singapore.

Instructions

Show StudentFirst (JCU Singapore): classes in the next 8 days with time and room, overall class and campus attendance against the 90% minimum, and each class with how many sessions were attended. Use when the user asks about their timetable, next classes, rooms or attendance at JCU Singapore.

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

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.

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 this a read-only, open-world operation, so the safety profile is covered. The description adds genuinely useful behavioral scope (a fixed 8-day forward window, a 90% threshold benchmark, aggregate plus per-class breakdown), but says nothing about login requirements, empty-result behavior, or whether data is cached/fetched live — relevant given a studentfirst_login sibling exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, and the substantive content comes first with the usage cue last. The first sentence is long and comma-chained, which slightly slows parsing, but every clause carries information.

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, the description usefully enumerates what will be returned (class times, rooms, attendance percentages, per-class session counts). It is sufficient for correct invocation, with the only real gap being prerequisites such as an authenticated session.

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% and the single optional 'account' parameter is documented in the schema itself, including a pointer to account listing. The description adds nothing about the account parameter, so baseline 3 applies.

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 states specific content: classes within the next 8 days with time and room, overall class/campus attendance against the 90% minimum, and per-class session attendance. This is a concrete verb+resource statement an agent can match against a user question. It stops short of distinguishing itself from the sibling studentfirst_class_attendance, which covers overlapping attendance ground.

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?

The final sentence gives explicit trigger conditions ('timetable, next classes, rooms or attendance at JCU Singapore'), which is clear usage context. It offers no exclusions or named alternatives, so an agent facing an attendance question has no stated reason to prefer this over the sibling attendance tool.

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