Skip to main content
Glama

uplus_login

Signs in to U+ through an attached browser session, supporting manual user login or automated credential entry with fallback when auto fill fails.

Instructions

Sign in to U+ through the attached browser session. Ask the user which flow they prefer BEFORE calling:

  • mode="manual": open the portal and wait for the user to sign in by themselves in the visible browser window; no account or password is needed.

  • mode="auto": the model first asks the user for their account, password and school name, then fills the sign-in form, submits and verifies the session. Credentials are used only for this call: never persisted to config, reports or logs, and never echoed back. The wait is capped at 30 s so a failed auto fill hands over to manual quickly. If auto fill cannot find the fields, the school selector cannot be matched, or a captcha / SMS / wrong-password prompt appears, fall back to manual and hand the window to the user.

Returns logged_in, the chosen mode, current URL and token length.

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

Input Schema

NameRequiredDescriptionDefault
modeNomanual
schoolNo
passwordNo
usernameNo
wait_timeout_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.2

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations provided, the description carries the whole burden and does so: it discloses the credential handling policy (used only for this call, never persisted to config/reports/logs, never echoed back), the 30 s cap on the auto wait, and the failure-handling handoff to a visible browser session. It also states the return payload (logged_in, chosen mode, URL, token length).

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 action and then the decision the agent must make, with two tight bullets covering each mode and a single paragraph of failure rules. Slightly verbose and the 30 s claim adds ambiguity rather than value, but nearly every sentence earns its place.

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?

For a 5-parameter, unannotated auth tool with no output schema, the description covers preconditions, both modes, failure paths, and return fields. Gaps remain around wait_timeout_ms and the already-logged-in case / relationship to uplus_check_login, which keep it from being fully self-sufficient.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate, and it does well for mode (enumerating 'manual' vs 'auto' semantics) and for username/password/school (tied to the auto flow). However, wait_timeout_ms is never mentioned, and the claim that 'the wait is capped at 30 s' sits uneasily against a default of 120000 ms, leaving the agent unsure whether that parameter matters.

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?

The description gives a specific verb and resource (sign in to U+ via the attached browser session) and immediately splits behavior into two named modes, so an agent can tell it apart from browse_* tools. It does not, however, distinguish itself from the sibling uplus_check_login, so an agent has to infer whether to sign in or just check status.

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 explicitly instructs the agent to ask the user which flow they prefer BEFORE calling, defines when each mode is appropriate, and enumerates exact fallback triggers (field not found, school selector mismatch, captcha/SMS/wrong password) that force a switch to manual. This is about as complete a when-to-use/when-not-to-use statement as a description can carry.

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