Skip to main content
Glama

检索秀米模板

xiumi_search_templates

Search the Xiumi template library by Chinese keyword and/or category ID to get template IDs, tags, and plain-text summaries. Use the returned IDs to insert a template.

Instructions

按中文关键词和/或分类 ID 检索秀米模板库,返回模板 ID、标签、纯文本摘要。结果会缓存,可直接把模板 ID 交给 xiumi_insert_template。

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

Input Schema

NameRequiredDescriptionDefault
limitNo返回条数,默认 8
queryNo中文关键词,如「引导关注」「节日标题」「分割线」
pageNoNo翻页,从 0 开始
tagIdsNo分类 ID,来自 xiumi_list_template_tags
includeHtmlNo是否返回模板 HTML(体积较大,默认 false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does disclose useful behavioral traits: it returns template IDs, tags, and plain-text summaries; it caches results; and it warns that they are suitable for direct insertion into xiumi_insert_template. Read-only behavior is implied by '检索' but not stated outright. Rate limits, error and empty-result behavior, and pagination semantics are unmentioned, leaving some gaps for a no-annotation tool.

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 sentences, front-loaded with the core search action, followed by the return payload and the workflow handoff. The caching note and the insertion pointer each earn their place; there is no filler.

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?

With no output schema, the description correctly states the shape of the result (ID, tags, plain-text summary) and the caching behavior. For a five-parameter, all-optional, no-annotation tool, that covers most of what an agent needs. Minor gaps include how paging behaves, what an empty result set looks like, and how costly includeHtml=true is.

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 all five parameters are already documented in the schema, which sets the baseline at 3. The description adds a small amount by clarifying that query and tagIds are combined with '和/或' and that the default return is a plain-text summary rather than HTML. It does not explain limit, pageNo, or the size tradeoff of includeHtml beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb and resource (检索秀米模板库) and states the inputs (中文关键词和/或分类 ID) and the returned fields (模板 ID、标签、纯文本摘要). It also names the natural next tool, xiumi_insert_template, so an agent can place this tool in the workflow without opening the schema.

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 definition states usage context clearly: this is the search step, and the '和/或' wording tells the agent that query and tagIds can be used together or separately. It also explicitly hands off to xiumi_insert_template for the following step. It lacks explicit guidance on when NOT to use it or which sibling to use instead for other lookups (for example, tag discovery via xiumi_list_template_tags is only implied through the tagIds reference in the schema).

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