baozhibao-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BAOZHIBAO_API_KEY | No | API Key,可选,用于默认登录 | |
| BAOZHIBAO_API_URL | Yes | API 服务地址,必填 |
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 |
|---|---|
| loginA | 使用 API Key 登录,获取认证 Token。这是使用其他工具前的第一步。 |
| add_itemC | 添加新物品。可以记录物品名称、存放位置、过期日期等信息。 |
| scan_add_itemA | 通过扫描条形码添加物品。系统会自动识别物品信息,用户只需补充存放位置等信息。 |
| query_itemsA | 查询物品列表。可以通过关键词、位置、状态等条件筛选。 |
| get_itemA | 获取物品详细信息。通过物品ID查询物品的完整信息。 |
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 5 tools
Most tools are distinct: login for auth, add_item for manual entry, scan_add_item for barcode entry, query_items for listing/searching, and get_item for details. The only potential confusion is between add_item and scan_add_item, but the barcode-specific description makes their purposes clear.
Tool names mostly follow a verb_noun pattern (add_item, query_items, get_item), with scan_add_item as a compound of that. 'login' is a slight deviation but is a common exception and doesn't disrupt the overall consistency.
With 5 tools, the server is well-scoped for basic item management. Each tool serves a necessary step in the workflow (auth, adding, querying, viewing details), and no tools feel redundant or excessive.
The server covers authentication, item creation (two methods), listing, and detail retrieval, but lacks update and delete operations. This is a notable gap for a full CRUD lifecycle, though agents could potentially work around it in limited scenarios.