Weather 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 |
|---|---|
| fetch_weatherC | Get weather information for a given location |
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 distinct as it is the only one available.
The single tool name follows a clear verb_noun pattern (fetch_weather), and with only one tool, consistency is inherently perfect as there are no other names to compare against.
A single tool is too few for a weather server's apparent scope, which typically involves multiple operations like forecasts, alerts, or historical data. This minimal set feels thin and limits functionality.
The tool surface is severely incomplete for a weather domain. It only provides current weather information, with obvious gaps such as missing forecasts, alerts, or location-based queries, which are essential for typical weather-related workflows.