Skip to main content
Glama

auth_setup

Opens a local browser setup page to configure PKU credentials, bind an OTP token, and test login; use it for first-time setup, password changes, or expired tokens.

Instructions

打开本机配置网页(只在 127.0.0.1),让用户在浏览器里填学号密码、绑定手机令牌、测试登录。

首次使用、换密码、令牌失效时调用。把返回的 url 告诉用户(浏览器通常已自动打开),等用户说完成后再调用 auth_status 确认。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the localhost-only (127.0.0.1) security boundary, that the operation is human-in-the-loop and must wait for the user, that a url is returned, and that the browser typically auto-opens. It stops short of saying what happens if the user abandons the flow or whether the call blocks, which keeps it from a 5.

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?

Two tight paragraphs: the first establishes what the page does, the second establishes when to call and what to do with the result. Nothing is redundant and the critical localhost constraint appears up front.

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?

An output schema exists, so return values need not be explained, yet the description still flags that a url comes back. For a parameterless interactive auth tool, an agent has everything needed: trigger conditions, the localhost scope, the user-wait requirement, and the auth_status confirmation step.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly does not waste words inventing parameter detail.

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 names a concrete verb and resource: it opens a local configuration web page bound to 127.0.0.1 where the user enters student ID/password, binds a mobile token, and tests login. That is far more specific than the tool name alone and cleanly separates it from sibling tools like auth_status, which it references by name.

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 states exactly when to call: first use, after a password change, or when the token is invalidated. It also spells out the follow-up protocol - pass the returned url to the user, note that the browser usually opens automatically, and only call auth_status after the user confirms completion - so the agent knows both the trigger and the next step.

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