Skip to main content
Glama

mystudent_page

Read-only

Reads a full MyStudent page or section in a hidden browser, covering details, study, finances, tasks, calendar or forms. Read-only; do saving, payments, enrolment and submissions on the website.

Instructions

Read one MyStudent page in full, in a hidden browser (about 10 s, plus 3-5 s for each section). Pages: details (personal details, contacts and addresses, educational background, sanctions, communications, forms); study (course structure, course overview, self-service reports on offer, withdrawal: census and last-withdrawal dates per subject); class_registrations; finances (summary, outstanding transactions and amounts payable, payment receipts, forms, payment preferences); tasks (enrolment tasks still to do); calendar (this week); forms (forms you can fill out); form_responses (your draft and submitted forms); applications (course applications and offers). Sections: details (summary, contacts, education, sanctions, communication, forms); study (course, overview, reports, withdrawal); class_registrations; finances (summary, transactions, receipts, forms, preferences); tasks; calendar; forms; form_responses; applications. Pass section to read only one (faster). This only reads: it never saves, requests, pays, enrols, withdraws or submits anything; tell the user to do those on the MyStudent website. Use when the user asks for something in MyStudent that mystudent_overview does not show in full.

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": {
      "page": "<page>"
    },
    "name": "mystudent_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageYesWhich page to read
accountNoSaved account to use (see learnjcu_list_accounts). Only needed when several accounts are saved and the user has not chosen one yet.
sectionNoOne section of the page, e.g. "contacts" on details or "withdrawal" on study; omit for all

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well past readOnlyHint/openWorldHint by disclosing runtime cost (~10 s, plus 3-5 s per section) and that it runs in a hidden browser, which explains latency and why section-scoping matters. It also enumerates exactly what it will never do (save, request, pay, enrol, withdraw, submit), closing the ambiguity that a read tool might trigger side effects.

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?

Front-loaded with verb, resource, and timing, and every clause is functional. However, the "Pages:" and "Sections:" lists largely restate the same content (finances, forms, class_registrations appear twice in near-identical form), which is redundant bulk an agent must parse twice.

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 read-only fetch tool with three parameters and no output schema, the page/section content map effectively stands in for return-value documentation, and timing is disclosed. The gap is authentication behavior: it never says what happens if no session exists or whether a login is required first, despite mystudent_login being a sibling and an `account` parameter being exposed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline would be 3, but the description adds substantial meaning the schema lacks: each enum value of `page` is expanded into its constituent content, and `section` is illustrated with concrete per-page examples ("contacts" on details, "withdrawal" on study). This directly supports choosing the right page/section combination.

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

Purpose5/5

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

Opens with a specific verb and resource ("Read one MyStudent page in full, in a hidden browser") and immediately enumerates the nine valid pages with what each contains. An agent can distinguish this from mystudent_overview without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: "Use when the user asks for something in MyStudent that mystudent_overview does not show in full," naming the sibling and the condition that selects this tool. It also gives an efficiency rule ("Pass section to read only one (faster)") and a hard boundary: writes must be done by the user on the MyStudent website.

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