Skip to main content
Glama

插入秀米模板

xiumi_insert_template

Insert a selected Xiumi template into the current article at the cursor or end, returning component IDs and text/image slots for later editing.

Instructions

把模板插入当前文章(追加到末尾),返回新增组件的 ID、文本槽和图片槽。插入后可用 xiumi_fill_text 填字、xiumi_set_image 换图。

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": {
      "templateId": "<templateId>"
    },
    "name": "xiumi_insert_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
atNo插入位置:end 追加到文末(默认),cursor 插入到当前光标处
templateIdYes模板 ID,来自 xiumi_search_templates

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden and usefully discloses that insertion appends to the article and returns new component IDs plus text and image slots. It does not explain side effects, prerequisites, or how cursor insertion differs from the default append behavior, leaving meaningful behavioral 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?

The description is two compact sentences, front-loaded with the action and followed by return values and next-step tools. Every sentence contributes useful information without repetition.

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 two-parameter mutation tool with no output schema, the description helpfully states what is returned: new component IDs and text/image slots. It is nearly complete, though it omits prerequisites and does not clarify the cursor-insertion path.

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 schema already documents templateId and the at enum, including end versus cursor. The description adds no parameter detail beyond the schema and its 'append to end' wording does not acknowledge the cursor option.

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 clearly states a specific verb and resource: insert a template into the current article and append it to the end. It also distinguishes the follow-up actions from xiumi_fill_text and xiumi_set_image. However, the parenthetical 'append to end' is slightly narrower than the schema, which also allows cursor insertion.

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 a clear post-insertion workflow by naming xiumi_fill_text for text slots and xiumi_set_image for image slots. The main gap is that it does not explicitly state prerequisites, such as needing the article open or obtaining templateId via xiumi_search_templates.

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