MCP-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-weather-forecastC | 根据经纬度获取天气信息 |
| get-github-userC | 根据用户名获取 Github 用户信息 |
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 with no overlap: one retrieves GitHub user information based on a username, while the other fetches weather forecasts based on geographic coordinates. An agent would have no difficulty telling these tools apart as they operate in entirely different domains.
Both tools follow a consistent verb-noun naming pattern (get-github-user and get-weather-forecast), using hyphens for separation. The naming is predictable and readable throughout the set.
With only 2 tools, the server feels thin and under-scoped for a general-purpose 'MCP-Server' name. The tools cover unrelated domains (GitHub and weather), suggesting a lack of cohesive focus rather than a well-defined purpose that justifies such a minimal set.
The tool surface is severely incomplete for any coherent domain. As a GitHub tool, it lacks basic operations like listing repos or issues; as a weather service, it misses features like historical data or alerts. The two tools together don't form a complete workflow for any identifiable purpose.