Skip to main content
Glama
qurioskill

weather

by qurioskill
OverviewSchemaRelated ServersScoreDiscussions
Python

mcp-python

A Model Context Protocol (MCP) server that exposes US weather data — via the National Weather Service API — as tools, resources, and prompts for MCP-compatible clients like Claude Desktop.

Features

Tools

  • get_alerts(state) — active weather alerts for a two-letter US state code (e.g. CA, NY)

  • get_forecast(latitude, longitude) — forecast for the next 5 periods at a given location

Resources

  • weather://states — list of valid two-letter US state codes

  • weather://alerts/{state} — alerts for any state, as a readable resource

  • Static alert resources for CA, NY, TX, FL (so they're attachable from Claude Desktop's picker, which only lists static resources)

Prompts

  • weather_briefing(state) — concise severe weather briefing for a state

  • trip_packing_advice(latitude, longitude) — packing advice based on the forecast for a location

Related MCP server: Weather MCP Server

Requirements

  • Python >= 3.11

  • uv

Setup

uv sync

Running the server

uv run weather.py

The server communicates over stdio, so it's meant to be launched by an MCP client rather than run standalone.

Using with Claude Desktop

Add to your Claude Desktop config (claude_desktop_config.json):

{
  "mcpServers": {
    "weather": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/mcp-python",
        "run",
        "weather.py"
      ]
    }
  }
}

Restart Claude Desktop and the weather tools, resources, and prompts will be available.

Project structure

  • weather.py — the MCP server (tools, resources, prompts)

  • main.py — placeholder entrypoint from the project template

  • pyproject.toml / uv.lock — dependencies, managed with uv

Available Tools

2 tools
get_alertsB

Get weather alerts for a US state.

Args:
    state: Two-letter US state code (e.g. CA, NY)
ParametersJSON Schema
NameRequiredDescriptionDefault
stateYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It doesn't mention return format, pagination, whether alerts are current or historical, severity levels, or any rate limits or auth requirements. For a read-type tool the lack of annotations leaves significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise and well-scoped. The description is two lines with an args docstring for the single parameter. Every word is functional with zero waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, which reduces the burden for explaining return values. However, with 0% schema description coverage, 1 single param (already covered in the args), no annotations, and no behavioral details (alert types, severity, expiration, update frequency), the description is minimal. For a weather alert tool, agents would benefit from knowing what constitutes an alert return vs. a no-alert return.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'state' is described in the argument docstring as a two-letter US state code with examples (CA, NY), which adds meaning beyond the bare schema. However, it doesn't specify case sensitivity, whether territories are included (e.g., DC, PR), or what happens for invalid state codes. The examples help but full semantics aren't covered.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool gets weather alerts for a US state, with a specific verb ('get') and resource ('weather alerts') and a geographic scope ('US state'). It distinguishes from the sibling tool 'get_forecast' by the resource type, though it doesn't explicitly name the sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context ('for a US state') but provides no when-to-use guidance, no exclusions, and no comparison to the sibling get_forecast tool. The intent is reasonably clear but the agent doesn't know when alerts vs forecast is more appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_forecastC

Get weather forecast for a location.

Args:
    latitude: Latitude of the location
    longitude: Longitude of the location
ParametersJSON Schema
NameRequiredDescriptionDefault
latitudeYes
longitudeYes

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It doesn't disclose how many days of forecast are returned, data freshness, caching behavior, rate limits, or what units (Celsius/Fahrenheit) are used. The description only restates the parameters without adding behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but under-specified rather than appropriately concise. The Args section is mostly unnecessary given the input schema repeats the same parameter names and types. The single opening sentence is useful, but the parameter documentation is redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is an output schema present, which helps, but the description still fails to communicate what the forecast contains or how comprehensive it is. For a tool that returns weather data, the agent has no sense of forecast length, granularity, or data fields without inspecting the output schema. The description is minimally sufficient for a basic 2-param lookup tool but leaves key context undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, meaning the description must compensate. The description merely restates that latitude/longitude are coordinates of the location, which adds marginal value over the schema. It doesn't explain valid ranges (e.g., -90 to 90, -180 to 180), precision requirements, or format expectations. Minimal semantic addition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Get weather forecast for a location' with a clear verb+resource. It doesn't distinguish from its sibling tool get_alerts, and 'forecast' vs 'alerts' distinction is implied but not explicit. The purpose is clear but missing scope details (time range, units).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs get_alerts. The description doesn't explain the distinction between getting a forecast and getting alerts, nor does it mention any special circumstances (e.g., use get_alerts for severe weather warnings). No when/when-not guidance is provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv0.1.0
    • First observedget_alerts
    • First observedget_forecast
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.9/5.0
Disambiguation5/5

The two tools are clearly distinct: get_alerts handles weather alerts for a US state, while get_forecast provides forecasts for specific coordinates. There is no ambiguity about which tool to use for which purpose.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (get_alerts, get_forecast) using the same verb 'get' and snake_case convention. The naming is perfectly consistent.

Tool Count2/5

With only 2 tools for a weather domain, the surface feels very thin. Weather servers typically need additional operations like current conditions, radar, air quality, or reverse geocoding to be genuinely useful.

Completeness2/5

The domain of weather covers more than alerts and forecasts. There are notable gaps: no current conditions, no historical data, no multi-day/hourly breakdown details, and no reverse geocoding for the coordinate-based forecast.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qurioskill/mcp-python-demo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server