Skip to main content
Glama

查看文章结构

xiumi_get_comps

Lists the current article's top-level components with IDs, text previews, and text-slot counts so you can verify layout order and identify which components need text.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the full behavioral burden. It does disclose useful behavior: the tool reads the current article, uses an implicit current-article context, and returns specific fields. However, it does not explicitly state that the tool is read-only, has no side effects, or what happens when no article is open. So it adds some value but leaves gaps.

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, tightly written sentence: the action and scope come first, then the returned fields, then the purposes. There is no redundant or filler wording.

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?

This is a simple read-only tool with no output schema and no annotations. The description lists the return fields, which is valuable in the absence of an output schema. Its only remaining gap is environmental behavior, such as what happens when no article is loaded.

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 schema has 0 parameters and 100% coverage, and the description correctly implies that no input is required because it targets the currently open article. With no params to explain, the baseline of 4 applies.

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 gives a specific verb and resource: it lists the top-level components of the current article. It also names the fields returned (ID, text preview, text slot count). This makes the tool's scope clear compared with the other 'xiumi_*' tools, but it does not explicitly distinguish itself from a sibling such as xiumi_get_html, so it stops short of a 5.

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?

The description states a clear use context: checking layout order and confirming which components to fill with text. These are concrete scenarios, not vague hints. It does not name alternatives or state when not to use it, which keeps it at 4 rather than 5.

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