Skip to main content
Glama
yukincom

Home Weather MCP

by yukincom

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

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
weather_list_locationsA

List up to three locations, their primary/alternate names, coordinates, and default status.

weather_search_placesA

Search a real place name for geographic candidates without changing settings.

Use country_code (JP by default) for the country. Check administrative regions when names are ambiguous. Japanese ward names use GSI as a fallback.

weather_set_locationA

Add a location requested by the user. Only location settings are persisted.

Example: alias=Office, place_name=Osaka, Japan, country_code=JP. At most three locations. additional_aliases supplies alternate names. make_default=true selects this location when alias is omitted in weather_get. Multiple geocoding matches are returned without saving; pass a selected candidate_id as a string. Use weather_update_location to modify an existing location.

weather_update_locationA

Update an existing location without adding a slot.

alias identifies the location using any current name. Changing place_name resolves new coordinates. new_alias renames the primary alias. additional_aliases replaces the alternate names; [] removes them. Omitted fields remain unchanged. make_default=true selects this place as the default. Ambiguous geocoding returns candidates without saving. Retry with the selected candidate_id as a string.

weather_remove_locationA

Remove a location as requested. Removing the default selects the first remaining location.

weather_getA

Fetch fresh weather for a registered primary or alternate name.

Omit alias to use the default (initially Tokyo). target: current, today, or tomorrow. Forecasts include temperature_range: value_c, threshold_c, is_large (>= threshold), and basis=daily_max_minus_min. Missing/invalid temperatures yield null value and flag. Includes rain intervals and temperature/umbrella advice. Today's rain covers the remaining hours. include_hourly=true adds hourly values. Units: Celsius, m/s, mm; timestamps use the location timezone. No weather storage, cache or scheduling. language=en|ja overrides the server default. Both summary_en and summary_ja are included for forecasts; summary and weather labels use the selected language.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool covers a distinct action: listing registered locations, searching geographic candidates, adding/updating/removing a location, and fetching weather. There is no overlap or ambiguity in purpose, and descriptions reinforce the boundaries.

Naming Consistency5/5

All tools share a weather_ prefix and follow a verb_noun pattern: list_locations, search_places, set_location, update_location, remove_location, and get. The lone weather_get is still clear because weather is the server's core resource.

Tool Count5/5

Six tools is well-scoped for a home weather server: four location management operations, one place search, and one weather retrieval. Every tool earns its place without redundancy.

Completeness5/5

Location lifecycle is complete (list, set, update, remove, plus search for candidates), and reading current/today/tomorrow forecasts with optional hourly data covers the weather use case. No obvious dead ends or missing core operations.

Maintenance

ActivityMaintained
ResponsivenessNo issues