Skip to main content
Glama
t1gerk1ngd0m

openweather-mcp

by t1gerk1ngd0m
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENWEATHER_API_KEYYesOpenWeatherMap API key, obtained from https://home.openweathermap.org/api_keys
OPENWEATHER_BASE_URLNoBase URL for OpenWeatherMap APIhttps://api.openweathermap.org/data/2.5

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_weatherA
指定された都市の現在の天気を取得します

Args:
    city: 都市名（例: Tokyo, London, New York）

Returns:
    天気情報のフォーマットされた文字列

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion or overlap between tools. The tool's purpose is clear and distinct from any potential alternatives.

Naming Consistency5/5

The single tool follows a standard and clear verb_noun naming pattern (`get_weather`). With only one tool, there is no inconsistency to evaluate, and the name is intuitive and readable.

Tool Count2/5

The server is named `openweather-mcp` but provides only one operation. This feels too few for the apparent scope of a weather service, which typically requires multiple endpoints (e.g., forecasts, air quality, historical data). The set is thin and likely insufficient for typical agent use cases.

Completeness2/5

The tool surface is severely limited, offering only current weather for a city. For a general weather API, significant operations such as forecasts, multi-day outlooks, or weather alerts are missing, leaving agents with limited capability and causing potential failures when those features are needed.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources