Skip to main content
Glama

studentfirst_login

Read-only

Sign in to StudentFirst or refresh an expired session when a StudentFirst tool reports an expired or missing session.

Instructions

Sign in to StudentFirst or refresh an expired session. Call this whenever a StudentFirst tool says the session expired or you are not signed in. StudentFirst (JCU Singapore) has its own user name and password, not the JCU single sign-on. When a window opens, ask the user to sign in there and to let the browser save the password, so later refreshes need nothing from them. 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": "studentfirst_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.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the behavior that actually matters: a silent refresh attempt first (a few seconds, no window), a fallback that opens the sign-in page in the default browser, the waitingForUser return state requiring a re-call, and per-account isolation of saved sessions. This is exactly the extra context annotations cannot express for an open-world interactive tool.

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 the purpose and trigger in the first two sentences, with operational details following in a sensible order. It is dense rather than bloated, though the browser-window instruction is stated twice ('When a window opens, ask the user to sign in there' and later 'tell the user a browser window opened and ask them to sign in there'), which is avoidable repetition in an otherwise efficient passage.

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, output-schema-less authentication tool with open-world side effects, the description covers everything an agent needs: when to invoke, credential ownership, ordering relative to learnjcu_login, browser interaction, the waitingForUser retry loop, and the do-not-ask-for-password rule. Nothing material is omitted.

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 beyond the schema for 'account': calling without it triggers a user prompt, and each saved account has its own independent sign-in. The 'waitSeconds' parameter is left entirely to the schema, which documents it adequately (default 45, 240 max), so no gap remains.

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?

States a specific verb and resource ('Sign in to StudentFirst') plus a second concrete function ('refresh an expired session'). It also positions the tool against siblings by noting StudentFirst uses its own credentials rather than JCU single sign-on and that accounts are created by learnjcu_login, so an agent can distinguish it from learnjcu_login without opening either 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 an explicit trigger ('Call this whenever a StudentFirst tool says the session expired or you are not signed in'), an ordering prerequisite ('sign in to LearnJCU first if none is saved'), and follow-up handling ('If the result says waitingForUser, call again after the user says they are done'). It also states a prohibition ('Never ask the user for their password'), which removes a likely agent error path.

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