Skip to main content
Glama

uoft_auth_status

Read-onlyIdempotent

Check connection and login progress for UofT services without exposing credentials or student records; refresh verifies saved cookies and returns plain-language status and next actions.

Instructions

Get connection and login progress without exposing credentials or student records.

refresh=True checks both services using saved cookies; it never opens a login window. A saved cookie is not proof of a valid session. last_verified is historical, not expiry. Each service reports a plain-language message, a kind, and a next_action.

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

Input Schema

NameRequiredDescriptionDefault
refreshNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.2

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: it discloses that no credentials or student records are exposed, that no login window is ever opened, and the important caveat that a saved cookie is not proof of a valid session and that last_verified is historical rather than an expiry. These are exactly the non-obvious behaviors an agent would otherwise guess wrong about.

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?

Four short lines, purpose front-loaded, then the parameter caveat, then the return shape. Some fragments ('last_verified is historical, not expiry') are terse but each sentence carries distinct information with no 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 describing the per-service return fields (message, kind, next_action). Minor gaps remain: it does not name the two services or state what happens when no cookies are saved at all.

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 0% and the schema offers only a defaulted boolean, so the description carries the full burden. It does so by explaining that refresh=True actively checks both services via saved cookies and never prompts, which implicitly defines the refresh=False behavior as a non-checking read.

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

Purpose4/5

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

Opens with a specific verb and resource: 'Get connection and login progress.' An agent can tell this apart from uoft_login and uoft_forget_session by the noun 'progress/status', though no sibling is named explicitly to make the boundary unambiguous.

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

Usage Guidelines3/5

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

Gives a clear condition for the refresh=True path ('checks both services using saved cookies; it never opens a login window'), which is real when-to-use guidance for the only parameter. However, it never says when to prefer this over uoft_login, or what a plain refresh=False call is meant for, leaving the alternative routing implicit.

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