MCP Weather 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 | Tool to fetch the weather of a 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 confusion or overlap between tools. The single tool 'fetch-weather' has a clearly distinct and unambiguous purpose.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'fetch-weather' follows a clear verb-noun pattern.
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 incomplete for the domain.
The tool surface is severely incomplete for a weather domain. It only provides current weather for a city, missing essential operations like forecasts, alerts, multi-location queries, or historical data, which will cause agent failures in broader tasks.