Git Spice Help 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-world-weatherC | 获取全世界的天气预报 |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as fetching worldwide weather forecasts, making it impossible to confuse with other tools.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'get-world-weather' follows a clear verb-noun pattern, which would be consistent if more tools existed.
A single tool is generally too few for most server purposes, as it limits functionality and scope. While weather-related servers could have more tools (e.g., for specific locations, forecasts, or historical data), one tool feels thin and underdeveloped for a comprehensive weather service.
The server's domain appears to be weather-related, but with only one tool for worldwide weather, there are significant gaps. Missing operations include getting weather for specific locations, historical data, forecasts by type (e.g., hourly/daily), or alerts, making the surface incomplete for typical weather use cases.