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 |
|---|---|
| weatherC | It fetches the latest weather reports for the given city. Args: city (str): The city name for which weather reports are required. Returns: dict: The weather reports for the given city. |
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 single tool has a clear, distinct purpose of fetching weather reports for a city.
The single tool name 'weather' is straightforward and descriptive. Since there is only one tool, naming consistency is inherently perfect with no deviations or mixed conventions to evaluate.
A single tool for a weather server is too few for the apparent scope, as it lacks essential operations like forecasts, historical data, or multi-location queries. This minimal set limits functionality and may cause agent failures in broader weather-related tasks.
The tool surface is severely incomplete for a weather domain, missing obvious gaps such as forecasts, alerts, or location-based searches. While it covers basic current weather, agents will struggle with common weather-related workflows due to these significant omissions.