Skip to main content
Glama
yuanbao-search-mcp

yuanbao-search-mcp

by bronya19c818

元宝搜索

yuanbao_search
Read-onlyIdempotent

Searches web pages for Chinese news, guides, encyclopedia entries, and real-time trends with site, vertical, and time filters. Returns titles, URLs, summaries, dates, relevance scores, and images.

Instructions

用腾讯云元宝搜索(WSA)检索全网公开网页,中文资讯、新闻、攻略、百科与实时热点表现好。支持限定站点、垂直领域与时间范围,返回标题、URL、摘要、发布时间、站点、相关性得分与配图。注意:本工具只返回摘要,不抓取网页正文;需要正文时请再对结果 URL 取页面内容。

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": {
      "query": "<query>"
    },
    "name": "yuanbao_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo结果类型:0 公开网页信源,1 优质权威垂直信源,2 混合;不传默认 0。
siteNo指定站点检索(如 qq.com),或用 exclude:a.com|b.com 排除站点,最多五个。
countNo返回条数,只支持 10 / 20 / 30 / 40 / 50,默认由服务端决定(通常 10)。
queryYes搜索词,例如「今天北京的天气」。
industryNo垂直领域:gov 政府,news 新闻,acad 学术,finance 财经。
deeplinksNo是否返回附件子链信息,仅旗舰版实例生效。
freshnessNo时效范围:dN 最近 N 天(1-30)、mN 最近 N 月(1-12)、yN 最近 N 年(1-5)、yyyy-mm-dd 指定日、yyyy-mm-dd,yyyy-mm-dd 区间。

Output Schema

NameRequiredDescriptionDefault
queryYes
totalYes
messageNo
resultsYes
request_idNo
service_versionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the bar is lower, yet the description adds genuinely new behavior: results are summaries only, no page-body fetch, and 'deeplinks 仅旗舰版实例生效' warns of an instance-dependent capability. Remaining gaps are minor (no rate limits or pagination behavior).

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?

Three tight sentences: purpose and strengths first, capabilities second, the summary-only caveat last — the most decision-relevant warning is front-loaded rather than buried. No filler or repeated phrasing.

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 7-parameter search tool with a rich schema, full annotation coverage, and an output schema, the description covers the essential unknowns: what kind of results come back and that page bodies require a follow-up fetch. Enumerating return fields is mildly redundant given the output schema, which keeps it just under 5.

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 explains mode, site syntax, count values, industry enums, and freshness formats. The description only restates the general capabilities (site restriction, vertical domain, time range) without adding syntax or edge-case meaning, so the baseline 3 applies.

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 ('用腾讯云元宝搜索(WSA)检索全网公开网页') and narrows scope to public web pages, plus states where it performs best (Chinese info, news, guides, encyclopedia, real-time hotspots). An agent knows exactly what it retrieves 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?

It gives a clear use context (Chinese-language, news, real-time, encyclopedia-style queries) and an explicit boundary: '本工具只返回摘要,不抓取网页正文;需要正文时请再对结果 URL 取页面内容' — a concrete when-not plus a next step. It does not name a sibling alternative for other query types, so it stops short of the top score.

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

Deploy Server

Other Tools