Skip to main content
Glama

登录秀米

xiumi_login

Opens the Xiumi login page, returns a screenshot, and waits for WeChat QR or password login, then reports whether authentication succeeded. Use it to authenticate before editing or saving articles.

Instructions

打开秀米登录页并返回截图。请在弹出的浏览器窗口里用微信扫码或账号密码完成登录;等待 waitSeconds 秒后返回是否登录成功。

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

Input Schema

NameRequiredDescriptionDefault
waitSecondsNo登录后最多等待多少秒,默认 0 表示立即返回

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 it discloses the key non-obvious traits: a browser window is opened, a human must complete authentication out-of-band, and the call blocks for up to waitSeconds before reporting success. It omits what happens if already logged in, whether the session persists, and whether the wait is polling or a fixed sleep.

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 short sentences: purpose and output first, then the required user interaction and timing. Every clause carries information; nothing is repeated from the tool name or schema.

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 single-parameter, no-output-schema tool, the description covers the flow, the human-in-the-loop requirement, and both return concepts (screenshot, success flag). It does not describe the shape of the returned screenshot or the exact result payload, which leaves a small gap given there is no output schema.

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% (min 0, max 300, default 0 meaning immediate return), so the structured field already explains the parameter. The description adds that the wait occurs after login is completed and precedes the success check, which clarifies the sequencing of the blocking behavior beyond the schema's plain wording.

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 action verb (打开登录页) and resource (秀米), and states the two results it produces: a screenshot and a login-success indicator. That is clearly distinct from siblings such as xiumi_start or xiumi_status, which do not involve an interactive login flow.

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?

It gives clear context for use: the agent must trigger this so the user can scan a WeChat QR code or enter credentials in the pop-up window, and something must be returned after the wait. It does not state when not to use it, e.g., what to do if a session already exists, or point at xiumi_status as a check-first alternative, so it falls short of a 5.

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