Skip to main content
Glama
ribomation

smhi-weather-forcast-mcp-server

by ribomation

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get-weather-forecastA

Get weather forecast for a specific location from SMHI. Returns forecast data for approximately 10 days ahead.

get-weather-observationsA

Get historical weather observations from a SMHI weather station.

list-weather-stationsB

List available SMHI weather stations for a specific parameter.

list-weather-parametersA

List all available weather parameters that can be queried from SMHI.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct resource and action: listing stations, listing parameters, fetching forecasts, and fetching observations. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb-noun pattern with lowercase and hyphens: list-weather-stations, list-weather-parameters, get-weather-forecast, get-weather-observations. The naming is uniform and predictable.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose. It covers metadata discovery and the two main data fetch operations without unnecessary bloat or thinness.

Completeness5/5

The tool surface covers the essential SMHI workflow: discover parameters, discover stations, get forecast, get observations. No critical dead ends are apparent for the stated domain.

Maintenance

ActivityInactive
ResponsivenessNo issues