Skip to main content
Glama

启动秀米编辑器

xiumi_start

Launch the dedicated browser with persistent login and open the Xiumi article editor, returning login status and current article info. Use on first run, after the browser closes, or to start a new blank article.

Instructions

启动专用浏览器(持久化登录态)并打开秀米图文编辑器,返回登录状态与当前文章信息。首次使用、浏览器被关闭或需要新开空白图文时调用。

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

Input Schema

NameRequiredDescriptionDefault
freshNotrue 时新开一篇空白图文;默认复用当前已打开的编辑器

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: the browser uses a persistent login state and the call reports login status and current article information. It does not state idempotency, what happens if a session is already running (only the parameter schema hints at reuse), or any latency or failure behavior.

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 sentences, action first, triggers second, with no filler. Every clause carries information the agent needs.

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 one-parameter session-bootstrap tool with no annotations and no output schema, the description covers purpose, triggers, and return values. The main gap is the absence of any note on precedence relative to the login and status siblings.

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 description coverage is 100%, so the single fresh parameter is already documented, and the baseline is 3. The phrase about needing a new blank article loosely maps to fresh=true, but it adds no format or edge-case detail beyond the schema.

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 names a specific action and resource: launching a dedicated browser with persisted login state and opening the Xiumi rich-text editor, plus what it returns (login status and current article info). It is clear on its own, but it does not distinguish itself from closely related siblings such as xiumi_login, xiumi_status, or xiumi_open_article, so the agent must infer the boundary.

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 explicit trigger conditions: first-time use, the browser has been closed, or a fresh blank article is needed. That is strong when-to-call guidance. It stops short of stating when not to call or naming an alternative (for example, checking xiumi_status first if a session may already exist).

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