yuanbao-search-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| YUANBAO_API_KEY | No | `TENCENTCLOUD_WSA_APIKEY` 的别名,同样用于传入元宝搜索服务 API KEY。 | |
| YUANBAO_BASE_URL | No | 覆盖接口域名。 | https://api.wsa.cloud.tencent.com |
| TENCENTCLOUD_WSA_APIKEY | No | 元宝搜索服务 API KEY,`sk-` 开头。 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yuanbao_searchA | 用腾讯云元宝搜索(WSA)检索全网公开网页,中文资讯、新闻、攻略、百科与实时热点表现好。支持限定站点、垂直领域与时间范围,返回标题、URL、摘要、发布时间、站点、相关性得分与配图。注意:本工具只返回摘要,不抓取网页正文;需要正文时请再对结果 URL 取页面内容。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool in the set, there is no possibility of tool selection confusion; its purpose (web search via Tencent Yuanbao WSA) is unmistakable. The description also clearly delineates what it does and does not do (snippets, not full page text).
The single name yuanbao_search follows a clean snake_case verb_noun-ish convention that matches the server name. There is no second tool to compare against, so full pattern consistency cannot be demonstrated, but nothing is inconsistent.
A single search tool is a defensible minimal surface for a focused search server, but it is thin: all query variations (site restriction, time range, vertical) must be expressed through one tool's parameters with no companion operations. The explicit note that full-text retrieval must happen elsewhere makes the one-tool surface feel incomplete rather than elegantly scoped.
Search coverage with filters and rich result metadata is reasonable, but the tool deliberately stops at snippets and tells the caller to fetch page content from the result URLs — a capability this server does not provide, creating a dead end for content-retrieval workflows. There is also no pagination or follow-up/refinement operation.