Skip to main content
Glama

删除组件

xiumi_delete_comp

Delete a top-level article component by ID to remove mistakenly inserted templates, extra blank lines, or dividers from Xiumi article layouts.

Instructions

删除文章里的一个顶层组件(按组件 ID)。适用于删除误插入的模板或多余的空行/分割线。

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "compId": "<compId>"
    },
    "name": "xiumi_delete_comp"
  }
}

Input Schema

NameRequiredDescriptionDefault
compIdYes组件 ID,来自 xiumi_get_comps 或 xiumi_insert_template

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/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 for a destructive operation. It never says whether deletion is permanent or reversible, whether child components go with the parent, whether an article must already be open, or whether a subsequent save is required. Only the '顶层组件' wording hints that nested content is removed along with the parent.

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: the action and its target first, then the motivating scenarios. Every phrase adds information, and there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter tool with full schema coverage and no output schema, the description covers what the tool does and when to reach for it. However, given it is a destructive operation with zero annotation support, the absence of permanence, undo, and follow-up-save information leaves a meaningful gap for an agent deciding whether to call it.

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% and there is a single parameter, compId, already documented in the schema, including its provenance from xiumi_get_comps or xiumi_insert_template. The description repeats that the operation is keyed by component ID but adds no format or validation detail beyond the schema, so the baseline 3 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: delete one top-level component in the article, identified by component ID. It also scopes the operation with '顶层组件', so the agent knows only top-level components qualify. It does not explicitly contrast with any sibling, but no sibling performs deletion, so the risk of confusion is low.

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 states concrete use cases: removing a template that was inserted by mistake, or extra blank lines/dividers. That is clear when-to-use context. It gives no when-not-to-use or alternative (for example, editing instead of deleting), 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.