Skip to main content
Glama
malkreide

srgssr-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SRF Meteo – 7-Tages-Prognose

srgssr_weather_forecast_7day
Read-onlyIdempotent

Get a 7-day Swiss weather forecast with daily min/max temperatures, precipitation, and conditions. Plan week activities or trips by querying coordinates.

Instructions

Liefert die tägliche Wettervorhersage der nächsten 7 Tage von SRF Meteo mit Min/Max-Temperatur, Niederschlag und Wetterlage pro Tag.

Wochenplanung, Tourismus-Empfehlungen, Trendanalysen.

Nur für Schweizer Standorte. Liefert maximal 7 Tage; Tage 1–3 sind deutlich verlässlicher als Tage 5–7.

latitude=47.3769, longitude=8.5417

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / $defs / WeatherForecastInput / properties / geolocation_id / anyOf
      Previous value: -[
-  {
-    "maxLength": 50,
-    "minLength": 1,
-    "pattern": "^[A-Za-z0-9_-]+$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 50,
+    "minLength": 1,
+    "pattern": "^[A-Za-z0-9_.,-]+$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / $defs / WeatherForecastInput / properties / geolocation_id / description
      Previous value: -"Optionale geolocationId aus srgssr_weather_search_location für präzisere Vorhersagen"New value: +"Optionale geolocationId aus srgssr_weather_search_location. Ohne Angabe wird sie aus latitude/longitude aufgelöst."
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations: the reliability drop-off (Tage 1–3 vs. 5–7) and the geographic limitation to Switzerland. This exceeds the baseline given annotation coverage.

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 compact and well-structured with a clear main sentence followed by tagged use_case, important_notes, and example sections. Each part earns its place, and the most critical information (what it does, Swiss scope, reliability) is front-loaded. No wasted words.

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

Completeness4/5

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

The description covers the main purpose, use cases, key constraints, and provides an example. Since an output schema exists, return-value details are not needed in the description. It lacks explicit differentiation from the 24h forecast tool, but the 7-day scope makes that implicit. Overall, an agent can call this tool correctly with the provided information.

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?

Schema description coverage is 0% for the top-level param, but the nested properties have descriptions. The tool description provides an example with concrete latitude/longitude values and notes the Swiss location constraint, which partially compensates for the low coverage. However, it does not explain the optional geolocation_id parameter or specify units for temperature/precipitation, so it doesn't fully compensate.

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 ('Liefert') and resource ('tägliche Wettervorhersage der nächsten 7 Tage von SRF Meteo') with concrete data fields (Min/Max-Temperatur, Niederschlag, Wetterlage). It clearly distinguishes from siblings like srgssr_weather_forecast_24h and srgssr_weather_current by specifying the 7-day horizon.

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?

The use_case section provides clear contexts (Wochenplanung, Tourismus-Empfehlungen, Trendanalysen) and the important_notes gives constraints (only Swiss locations, reliability window). However, it does not explicitly mention alternatives or when not to use this tool versus siblings, so it lacks explicit exclusions.

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

Deploy Server

Other Tools