Skip to main content
Glama

雨课堂扫码登录

ykt_login

Obtains a QR code and waits for scan confirmation to log into Yuketang, returning the code as text and an image path. Select the account's correct regional deployment.

Instructions

获取二维码并等待扫码确认。二维码以文本形式返回(可直接在终端显示),同时给出图片文件路径。四个区域(standard/hetang/changjiang/huanghe)的会话互不通用,请选择账号实际所在的区域。

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

Input Schema

NameRequiredDescriptionDefault
regionNo雨课堂区域standard
timeoutSecondsNo等待扫码的秒数

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose key behavior: the call blocks waiting for scan, returns the QR both as terminal-displayable text and as an image file path, and sessions are region-scoped and non-interchangeable. It omits what happens on timeout/expiry or whether a session is persisted, 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?

Three short sentences, no padding, and the core action plus the return format are front-loaded before the region caveat. Every sentence carries distinct information.

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 and no annotations, the description does the necessary work by explaining return values (QR text plus image path) and the interactive blocking nature. The main gap is failure behavior, such as timeout expiry or what state remains after an unsuccessful scan.

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 100%, so the schema already defines both parameters, but the description adds genuine meaning by explaining that region determines session isolation across the four enumerated values. timeoutSeconds is left entirely to the schema, but the region semantics are a real value-add beyond structured fields.

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 states a specific two-step action: fetch a QR code and wait for scan confirmation, which is unmistakably distinct from the sibling session tools (ykt_status, ykt_logout). It never names a sibling to contrast against, but the blocking-login purpose is 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?

Usage is implied rather than stated: the agent can infer this is the entry point when no session exists, and the description warns to pick the region matching the account. There is no explicit when-to-use/when-not-to-use guidance or mention of checking ykt_status first.

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