bososo-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bososo_searchA | 按关键词搜索网盘资源（夸克/UC/百度/迅雷等），返回带 token 的结果列表。这是获取资源的第 1 步；要用 bososo_get_resource 取回可保存的分享链接，必须使用本工具返回的 token。注意：搜索需要一点时间把结果找全（通常 20~40 秒），本工具会等到结果齐了再返回，耗时较长属正常，不要因为慢就重复调用。 |
| bososo_get_resourceA | 用 bososo_search 返回的 token 换取一份可保存的分享链接。这是获取资源的第 2 步，token 只能来自 bososo_search 的结果，不能自行构造。该操作服务端要真实处理一次、耗时较长；短时间内请求过多时会被要求先完成一次安全验证（返回 CAPTCHA_REQUIRED）—— 这种情况只能由用户在浏览器里手动完成验证，不要反复重试。 |
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 2 tools
The two tools map onto distinct, explicitly-numbered stages of a single workflow: bososo_search (step 1, keyword search returning tokens) and bososo_get_resource (step 2, token redemption). Their descriptions explicitly state the dependency (token must come from search), leaving no room for misselection.
Both tools use the same bososo_ snake_case prefix with a clear action component (search, get_resource). The pattern is predictable and consistent.
Two tools is on the lean side, but for a narrowly-scoped search-then-redeem pipeline each one earns its place with a distinct role. It is slightly under the typical 3-15 range but not a mismatch for the stated purpose.
The full end-to-end flow (find resources, exchange token for a savable share link) is covered with no dead ends. Minor gaps exist — no pagination, result filtering, or resource metadata/browsing — but agents can work around these via the search tool.