Skip to main content
Glama

uoft_login

Starts an official UofT browser sign-in for Degree Explorer, ACORN, or both, reusing saved sessions and returning immediately so you can complete Duo.

Instructions

Start official UofT browser login, returning immediately while you complete Duo.

service is degree_explorer, acorn, or both. Saved sessions are reused when valid. UofT requires a separate sign-in per service, so both means two logins in one window. Newly verified browser sessions wait five seconds, recheck access, and save the latest session before continuing or closing. Status stays in_progress during the wait. remember=False starts a fresh memory-only session without deleting saved sessions. Never supply passwords or MFA codes through tools. Check uoft_auth_status for progress.

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

Input Schema

NameRequiredDescriptionDefault
serviceNoboth
rememberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnly=false, idempotent=false, destructive=false; the description adds substantial context beyond that — immediate return, per-service sign-in separation, two logins in one window for 'both', a five-second post-verification wait with status staying in_progress, and that remember=False does not delete saved sessions. These are exactly the behavioral traits an agent needs to sequence subsequent calls correctly.

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 core action and the immediate-return contract, and most sentences earn their place. The five-second wait/recheck/save sentence is mechanically dense and could be tightened, but it is relevant timing information rather than filler.

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?

With no output schema, the description compensates by explaining that the call returns immediately and that progress lives in uoft_auth_status, which is enough for an agent to drive the flow. It does not say what the immediate return value actually contains (handle, URL, or status), a minor remaining gap.

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 description coverage is 0%, so the description must carry both parameters, and it does: it enumerates the service values and explains the non-obvious semantics of 'both' (two logins in one window), plus the meaning of remember=False (memory-only session, saved sessions untouched). That is more than the enum/defaults convey on their own.

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 ('Start official UofT browser login') and immediately qualifies the calling model ('returning immediately while you complete Duo'), which tells the agent this is an async kickoff rather than a blocking auth call. It also names the sibling that tracks progress (uoft_auth_status), so it is distinguishable from the rest of the auth family 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 Guidelines4/5

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

Gives concrete operational guidance: check uoft_auth_status for progress, never pass passwords or MFA codes, and use remember=False for a throwaway session. Saved-session reuse is described but there is no explicit statement of when not to call it (e.g., if already authenticated) or what to do if a session is already valid.

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