Skip to main content
Glama

mystudent_login

Read-only

Sign in to MyStudent or refresh an expired session when a MyStudent tool reports you are signed out; saved JCU single sign-on accounts are reused and a browser handles any required login.

Instructions

Sign in to MyStudent or refresh an expired session. Call this whenever a MyStudent tool says the session expired or you are not signed in. MyStudent uses the same JCU single sign-on as LearnJCU, so this is usually silent. Each saved account has its own sign-in; with several, pass account (the user is asked when you leave it out). Accounts are created by learnjcu_login; sign in to LearnJCU first if none is saved. It first refreshes silently (a few seconds, no window). If the user has to sign in, it opens the sign-in page in their default browser: tell the user a browser window opened and ask them to sign in there. If the result says waitingForUser, call again after the user says they are done. Never ask the user for their password; they type it in the browser.

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

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.
waitSecondsNoHow long to wait for the sign-in to finish before returning (default 45, which fits the 60 s default tool timeout of Codex)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that — a silent refresh that takes a few seconds, a browser window opening in the user's default browser, and an instruction to tell the user a window opened. The waitingForUser signal and the no-password rule are exactly the operational detail annotations cannot convey. Minor deduction because it never says what a successful result looks like beyond the absence of waitingForUser.

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 purpose and trigger, then prerequisites, then the interaction sequence — a sensible order for an agent reading top-down. Dense but nearly every clause carries an instruction; the only mild redundancy is 'usually silent' followed by 'It first refreshes silently (a few seconds, no window)'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter authentication tool with no output schema, this covers the full lifecycle: silent refresh, browser fallback, user interaction, re-call after waitingForUser, and the account prerequisite. Nothing an agent needs in order to call it correctly at the right moment is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema does not: each saved account has its own sign-in, and omitting account causes the user to be prompted rather than a failure. waitSeconds is left to the schema, which is acceptable given its clear description.

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 pair ('Sign in to MyStudent or refresh an expired session') and immediately scopes the tool against the sibling auth flow by noting that accounts come from learnjcu_login and LearnJCU must be signed in first. An agent can distinguish this from learnjcu_login and studentfirst_login 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?

Gives explicit triggers ('whenever a MyStudent tool says the session expired or you are not signed in'), prerequisites (sign in to LearnJCU first if no account is saved), and a retry rule ('If the result says waitingForUser, call again after the user says they are done'). It also states the exclusion that the agent must never request the password itself.

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