MCP TypeScript Demo 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 |
|---|---|
| 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 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, which clearly indicates their purpose. The minor deviation is that one description is in Chinese and the other in English, but the naming structure itself is uniform.
With only two tools, this server feels thin and under-scoped for a general-purpose demo. It lacks the depth or breadth expected for a meaningful toolset, making it appear incomplete or trivial.
The server covers two unrelated domains (date and weather) but lacks any cohesive scope. There are significant gaps in both domains—no date manipulation beyond basic relative units and no weather-related operations like forecasts or historical data—making it feel like a random collection rather than a complete surface.