Skip to main content
Glama

learnjcu_login

Read-only

Sign in to LearnJCU or refresh an expired session when LearnJCU tools report you are signed out; opens the default browser for authentication when needed.

Instructions

Sign in to LearnJCU or refresh an expired session. Call this whenever a LearnJCU tool says the session expired or you are not signed in. Each saved account has its own sign-in; with several, pass account (the user is asked when you leave it out). 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": "learnjcu_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.
newAccountNoSign in someone else and save them as another account
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.9/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 carries all the real behavioral detail an agent needs — a silent refresh that takes a few seconds with no window, escalation to the default browser, the instruction to tell the user a window opened, and the explicit prohibition on asking for passwords. The waitingForUser state and the re-call loop are disclosed behavior an agent could not derive from the schema or annotations. The only mild tension is that signing in and saving a new account writes a session, while readOnlyHint implies no persistent change, but that is a nuance rather than a contradiction of the description.

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

Conciseness5/5

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

Six short sentences, front-loaded with the purpose and trigger before the mechanics. Each sentence delivers a distinct instruction — trigger, account selection, silent phase, browser phase, retry loop, password rule — with no restatement of the tool name or filler.

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?

With no output schema and zero required parameters, the description still covers the full lifecycle an agent must handle: the silent attempt, the browser interaction, the waitingForUser return state, and the re-invocation rule. An agent can complete a sign-in end-to-end using only this text plus the schema.

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 description coverage is 100%, so the baseline is 3, but the description goes further by explaining the account parameter's fallback behavior — the user is prompted when it is omitted — which is operational meaning the schema only hints at. It does not discuss waitSeconds or newAccount in prose, leaving those two to the schema, which keeps it below a 5.

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?

The description states a specific verb and resource — 'Sign in to LearnJCU or refresh an expired session' — and scopes it to the LearnJCU family, which is precisely what distinguishes it from mystudent_login and studentfirst_login. An agent can route to it without inspecting 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?

It gives an explicit trigger ('whenever a LearnJCU tool says the session expired or you are not signed in'), a multi-account branch ('with several, pass account'), and a retry protocol ('if the result says waitingForUser, call again after the user says they are done'). Nothing about when to invoke it or what to do next is left to inference.

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