Skip to main content
Glama
VISHAL-MK

MCP Weather Server

by VISHAL-MK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MCP Weather Server

A simple MCP (Model Context Protocol) server built during an Agentic AI Internship. This server demonstrates how MCP can be used to provide tools, resources, and prompts to AI applications.

Features

MCP servers can provide the following functionalities:

Resources

File-like data that can be read by clients, such as API responses or file contents.

Tools

Functions that can be called by Large Language Models (LLMs) with user approval.

Prompts

Pre-written templates that help users accomplish specific tasks efficiently.

Related MCP server: Weather Service MCP

Requirements

  • Python 3.10 or higher

  • uv package manager

  • Python MCP SDK 1.2.0 or higher

  • httpx

Project Setup

1. Install uv

curl -LsSf https://astral.sh/uv/install.sh | sh

2. Initialize the Project

uv init .

3. Install Dependencies

uv add "mcp[cli]" httpx

4. Create the Server File

Create a file named weather.py and add the MCP server implementation.

5. Run the Server

uv run weather.py

Project Structure

.
├── weather.py
├── pyproject.toml
├── uv.lock
├── README.md
└── .gitignore

Learning Outcomes

  • Understanding MCP architecture

  • Building custom MCP tools

  • Integrating APIs using Python

  • Running MCP servers with uv

  • Working with Agentic AI applications

Author

Vishal M K B.E. CSE (AI & ML)

Available Tools

1 tool
get_alertsA

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

A4.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' implies a read-only operation, but the description does not explicitly state side-effect-free behavior or any caveats about alert types or data source. It is not misleading, but it adds minimal behavioral context beyond what the name implies.

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?

The description is extremely concise, with a front-loaded purpose statement followed by a compact Args block. Every sentence earns its place and there is no filler.

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

Completeness5/5

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

With a single well-documented parameter, an output schema, and no siblings, the description plus schema fully covers what an agent needs to invoke the tool correctly. No missing context for this simple operation.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description fully compensates by specifying the parameter format ('Two-letter US state code') and providing concrete examples ('CA, NY'). This adds real meaning beyond the raw schema type string.

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

Purpose5/5

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

The description states a specific verb ('Get'), a clear resource ('weather alerts'), and a clear scope ('US state'). It is unambiguous and leaves no doubt about what the tool does, even without siblings to differentiate from.

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

Usage Guidelines4/5

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

There are no sibling tools, so explicit routing guidance is unnecessary. The description clearly implies usage: when you need weather alerts for a US state. It lacks explicit exclusions, but nothing is misleading or missing for a tool of this simplicity.

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.

  1. 1 tool updatev0.1.0
    • First observedget_alerts
Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no ambiguity. The tool name and description clearly convey its purpose.

Naming Consistency5/5

The single tool uses a clear verb_noun pattern (get_alerts), which is consistent and appropriate.

Tool Count2/5

One tool is significantly fewer than expected for a weather server, which typically includes forecasts, current conditions, and other weather data. The server seems under-scoped.

Completeness2/5

The server only provides alerts for US states, missing core weather functionalities like forecasts, current conditions, or radar. This is a severe gap for a weather server.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers