Skip to main content
Glama

读取编辑器状态

xiumi_status

Read the current Xiumi editor state to check login status, article ID, title, component and text-slot counts, and body preview for layout editing decisions.

Instructions

读取当前秀米编辑器状态:是否登录、文章 ID、标题、组件数、文本槽数量与正文预览。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It does disclose the exact information returned, which is genuinely useful for a zero-parameter tool, and "读取" implies a safe read. However, it does not say what happens when the editor is not open or the user is not logged in (error vs. partial/null fields), which is the main behavioral unknown.

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?

A single front-loaded sentence with the resource first and the returned fields listed after a colon. Nothing is redundant and no sentence fails to earn its place.

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 simple zero-parameter read tool with no output schema, enumerating the returned fields effectively substitutes for a return-value spec. The only gap is failure/empty-state behavior when no article or session is active, which an agent would want to know before calling it as a precondition check.

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 the baseline is 4 and there is nothing for the description to disambiguate. No parameter meaning is lost.

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?

"读取当前秀米编辑器状态" states a specific verb and resource, and the enumeration (login status, article ID, title, component count, text slots, body preview) makes clear it is a status snapshot rather than content retrieval like xiumi_get_comps or xiumi_get_html. It does not explicitly name those siblings as alternatives, so differentiation is inferred rather than stated.

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?

There is no explicit when-to-use or when-not-to-use statement, and no sibling is named. Usage is only implied: an agent can reason that a status probe is useful before or after operations such as xiumi_login or xiumi_save, but the description never says so.

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