Start the local web admin console for mkeys to manage credentials, verify logins, issue temporary tokens, and view usage statistics. Returns a one-time access URL bound to 127.0.0.1.
启动（或复用）mkeys 本地 Web 管理台并返回带一次性访问令牌的访问地址（仅绑定 127.0.0.1）。页面上可以图形化管理凭据（增删改查、表单添加）、在线验证登录、签发临时令牌、查看使用统计图表。用户说'打开/看 mkeys 管理页面'或需要图形界面管理凭据时调用。
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden and provides meaningful behavior: it starts or reuses a local console, returns a one-time access token URL, and binds only to 127.0.0.1. It does not mention process lifecycle or token expiry, but the key side effects and security scoping are disclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the core action and return value. The second sentence lists GUI capabilities, which helps an agent decide between this tool and the sibling CLI-style tools, though the list is slightly enumerative.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with no output schema, it explains the return value (access URL with one-time token), the localhost binding, and the invocation trigger. Minor gaps remain around prerequisites and lifecycle/cleanup, but an agent has enough to select and call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the baseline is 4. The description adds no parameter-level details, and none are needed.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific action and resource: 启动（或复用）mkeys 本地 Web 管理台并返回带一次性访问令牌的访问地址. It clearly distinguishes itself from the sibling credential/verification tools by positioning itself as the GUI admin surface rather than a programmatic operation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly gives trigger conditions: 用户说'打开/看 mkeys 管理页面'或需要图形界面管理凭据时调用. It does not explicitly name alternatives or when-not cases, but the contrast with the programmatic sibling tools is clear enough.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.