Real-Time 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_weatherB | Get real-time weather information for a specified location (e.g., "Paris", "New York", "Tokyo"). Args: location: City or location name. detailed: If True, includes feels-like temperature, humidity, wind, and precipitation. |
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
There is only one tool, so there is no risk of confusing it with another. Its purpose is clearly stated and distinct.
The single tool follows a clear verb_noun pattern: check_weather. There are no competing conventions to create inconsistency.
A single tool is thin for a server, even one focused on real-time weather. The detailed flag helps, but the surface feels minimal.
For current real-time weather, the tool covers essential output including optional detailed metrics. It lacks features like forecasts, alerts, or multiple locations, but those may be outside the stated real-time scope.