MCP Server Demo
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 |
|---|---|
| get_current_weatherC | Get weather info for a given city. |
| get_current_dateB | 获取当前日期, 如果用户没有提供日期, 则返回当前日期, 如果用户提供的是相对单位, 如前天, 昨天, 明天, 则返回相对单位后的日期 |
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 handles date calculations and retrieval, while the other provides weather information. There is no overlap in functionality, making it impossible to confuse them.
Both tools follow a consistent 'get_current_*' naming pattern, using snake_case and starting with the same verb 'get'. This makes the set predictable and easy to understand.
With only two tools, the server feels thin and under-scoped for a general-purpose demo. It lacks coverage for common tasks beyond dates and weather, suggesting an incomplete or narrowly focused implementation.
The server's domain appears to be general utility or information retrieval, but it only covers dates and weather. There are significant gaps, such as time, location, or other common data queries, leaving agents with limited functionality.