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 |
|---|---|
| get-weatherC | Tool to get the weather for a 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 tool's purpose is clearly defined as getting weather for a city, making it distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'get-weather' follows a clear verb-noun pattern, which is appropriate for its function.
One 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 incomplete and may limit agent functionality.
The tool surface is severely incomplete for a weather domain. It only provides current weather for a city, lacking essential operations such as forecasts, alerts, historical data, or multi-location queries, which will likely cause agent failures.