Skip to main content
Glama

mystudent_study_plan

Read-only

Retrieve your course structure and subject statuses, including advanced standing, to check degree progress, see remaining subjects, and confirm current enrolments.

Instructions

Show your course in MyStudent and every subject in its structure with its status: enrolled (and in which study period), completed, exempt or credited, or planned for a later period, plus advanced standing. Takes about 10 seconds (the page is rendered in a hidden browser). Use when the user asks about their degree progress, which subjects are left, or what they are enrolled in.

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

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 readOnlyHint and openWorldHint, so the safety profile is covered. The description usefully adds that it takes about 10 seconds because the page is rendered in a hidden browser, which is real context an agent needs for timeout expectations, but it says nothing about auth prerequisites or failure modes.

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, front-loaded with what is returned before the latency note and usage triggers. The status enumeration is dense but each item earns its place by telling the agent what values to expect.

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?

No output schema exists, so the description must convey the return shape, and it does by enumerating the possible statuses and mentioning advanced standing. Latency and rendering behavior are also disclosed, leaving only authentication and error semantics unstated.

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?

The single optional 'account' parameter has 100% schema description coverage, so the schema carries the meaning entirely. The description adds nothing about account selection, which meets the baseline for high schema coverage.

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?

Specific verb ('Show') and resource (course structure with every subject and its status), plus a concrete enumeration of the status values returned. It reads distinctly from generic siblings like mystudent_overview or mystudent_status, although it does not name them explicitly.

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?

Gives clear triggering conditions: degree progress, which subjects are left, what the user is enrolled in. It does not say when NOT to use it or point to an alternative sibling for adjacent questions, so it stops short of full routing guidance.

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