Skip to main content
Glama
MinhHieu-Nguyen-dn

Weather MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

NameDescription
get_alertsB

Get weather alerts for a US state.

Args:
    state: Two-letter US state code (e.g. CA, NY)
get_forecastC

Get weather forecast for a location.

Args:
    latitude: Latitude of the location
    longitude: Longitude of the location
server_infoB

Get information about the current Weather MCP server configuration.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: get_alerts retrieves alerts for a US state, get_forecast provides forecasts for geographic coordinates, and server_info returns server configuration details. There is no overlap in functionality, making tool selection straightforward for an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with snake_case (get_alerts, get_forecast, server_info). The naming is predictable and readable, with no deviations in style or convention across the set.

Tool Count3/5

With only 3 tools, the server feels thin for a weather domain, as it lacks operations like historical data, radar imagery, or air quality. While the tools cover basic alerts and forecasts, the scope is limited, potentially requiring agents to work around missing functionality.

Completeness2/5

The tool set has significant gaps for a weather server. It provides alerts and forecasts but lacks update or delete operations, historical data access, or support for multiple locations. This incompleteness may lead to agent failures when more comprehensive weather data is needed.

Maintenance

ActivityInactive
ResponsivenessNo issues