MCP Communication Server
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 |
|---|---|
| addC | Add two numbers |
| open_web_pageA | 在IDE中打开一个新的网页窗口显示指定的URL，并自动等待接收页面发送的WebSocket数据 |
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 have completely distinct purposes: one performs a mathematical operation (adding numbers), while the other handles web page interaction (opening a URL and managing WebSocket data). There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
The naming is inconsistent: 'add' uses a simple verb without a noun, while 'open_web_page' follows a verb_noun pattern. This mixed convention lacks a predictable structure, though both names are readable. The inconsistency could cause minor confusion in a larger set.
With only 2 tools, the server feels thin for a 'Communication Server' domain, which typically implies broader functionality like messaging, notifications, or data exchange. The tools cover basic math and web display but lack operations for communication workflows, making the count insufficient for the apparent scope.
The server is severely incomplete for a communication domain. It lacks core operations such as sending/receiving messages, managing connections, or handling events. The existing tools (add and open_web_page) do not align with communication tasks, leaving significant gaps that would cause agent failures in typical use cases.