MCP-BOS
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| server_infoC | 获取服务器信息 Args: ctx: MCP上下文 Returns: dict: 服务器信息 |
| my_toolD | 自定义工具 |
| addC | 两个整数的和相加 |
| helloC | 返回问候消息 Args: name: 要问候的名称 Returns: str: 问候消息 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| hello_prompt | 创建一个问候提示 Args: name: 要问候的名称 Returns: str: 问候提示 |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| my://resource | |
| hello://greeting |
TDQS
Scored across 4 tools
The tools are highly ambiguous and overlapping in purpose. 'add' performs arithmetic, 'hello' returns a greeting, 'my_tool' is described only as 'custom tool' with no clear purpose, and 'server_info' retrieves server metadata. 'my_tool' is completely undefined, making it impossible to distinguish from others, and the set lacks clear domain boundaries, leading to high misselection risk.
Naming is inconsistent with mixed conventions. 'add' and 'hello' use simple verb forms, 'my_tool' uses a vague noun phrase, and 'server_info' uses a noun_verb pattern. There is no predictable naming scheme across the set, though all names are readable in English.
With only 4 tools, the count feels too thin for any coherent domain. The tools span arithmetic, greetings, an undefined custom function, and server metadata, suggesting a poorly scoped utility set rather than a focused server purpose. This minimal count does not adequately cover a meaningful operational surface.
The tool set is severely incomplete for any inferable domain. If interpreted as a general utility server, it lacks basic operations like subtraction, multiplication, or data processing. The inclusion of 'my_tool' without description creates a dead end, and there are significant gaps that will cause agent failures due to missing core functionalities.