Weather Service MCP
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_weatherC | Get the current weather for a given location. Args: location: The name of the city or location to get weather for Returns: A string describing the current weather conditions Note: This is a mock implementation. In production, integrate with a real weather API like OpenWeatherMap, WeatherAPI, or similar services. |
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 that cannot be confused with any other tool in the set.
The single tool follows a clear verb_noun pattern (get_weather), and with only one tool, there is perfect consistency. There are no other tools to create naming conflicts or inconsistencies.
A single tool is too few for a weather service domain, which typically requires operations like forecasts, historical data, or multiple location queries. This feels thin and incomplete for the apparent scope of a weather service.
The tool surface is severely incomplete for a weather service. While get_weather provides current conditions, there are obvious gaps such as missing forecast retrieval, historical weather data, or multi-location queries, which will limit agent capabilities in this domain.