Skip to main content
Glama
malkreide

srgssr-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SRF Meteo – Aktuelles Wetter

srgssr_weather_current
Read-onlyIdempotent

Get current weather for any Swiss location with temperature, wind, precipitation, and humidity from SRF Meteo. Use it for real-time conditions to plan outdoor activities or enrich editorial content.

Instructions

Liefert die aktuelle Wettersituation von SRF Meteo für einen Schweizer Standort (Temperatur, Wettercode, Wind, Niederschlag, Luftfeuchtigkeit).

Echtzeit-Wetterabfragen für Outdoor-Aktivitäten, Verkehrsmeldungen, Energieprognosen oder kontextuelle Anreicherung von redaktionellen Inhalten.

Nur für Schweizer Standorte (Latitude 45.8–47.9, Longitude 5.9–10.5). geolocation_id aus srgssr_weather_search_location empfohlen.

latitude=47.3769, longitude=8.5417 (Zürich)

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, idempotentHint=true, and destructiveHint=false. The description adds non-annotated behavioral context: the Swiss-only coordinate bounds, the recommendation to use geolocation_id from srgssr_weather_search_location, and the data fields returned. No contradiction with annotations; the description complements them well.

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 main sentence is dense and informative, and the use_case, important_notes, and example are cleanly separated with XML tags. Every section contributes operational value (purpose, scenarios, constraints, example) and there is no filler or redundancy.

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?

Given the output schema exists and annotations already cover safety properties, the description supplies the remaining practical context: use cases, geographic restrictions, and a tool relationship. It is complete enough for correct invocation; minor details like measurement units are not necessary for calling the tool successfully.

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 reported as 0% at the top level, though nested properties do have descriptions. The description compensates by providing a concrete coordinate example (Zürich) and the valid lat/lon ranges, and it clarifies the source of geolocation_id. It does not explain the 'params' wrapper or elaborate on parameter types beyond what the schema already contains, so coverage is moderate rather than comprehensive.

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 opens with a specific verb 'Liefert' and a precise resource: 'aktuelle Wettersituation von SRF Meteo für einen Schweizer Standort', followed by the returned data fields. The term 'aktuelle' plus the listed siblings (forecast_24h, forecast_7day) make the distinction between current weather and forecasts clear without needing to inspect schemas.

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 explicitly lists suitable scenarios (outdoor activities, traffic reports, energy forecasts, editorial enrichment), and the <important_notes> section gives a geographic boundary and recommends geolocation_id from srgssr_weather_search_location. It does not explicitly say 'use forecast tools for future conditions', but the sibling names and 'aktuelle' strongly imply the boundary.

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