Skip to main content
Glama
Sign In
malkreide

srgssr-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SRG SSR Audio – Radiosendungen auflisten

srgssr_audio_get_shows
Read-onlyIdempotent

List radio shows and podcasts from an SRG SSR channel by providing its channel ID, enabling catalog browsing. Filter shows by starting letter or paginate results.

Instructions

Listet Radiosendungen eines SRG SSR Radiokanals auf.

<use_case>Katalog-Browsing für Radio- und Podcast-Formate.</use_case>

<important_notes>Die API listet Radiosendungen nur pro Kanal — channel_id ist Pflicht und stammt aus srgssr_audio_get_livestreams. Innerhalb eines Kanals sind die Sendungen nach Anfangsbuchstabe gruppiert: ohne character_filter werden alle 27 Buchstaben abgefragt und zusammengeführt, mit character_filter ist es eine einzige Abfrage. Audio-Kataloge enthalten häufig auch reine Podcasts.</important_notes>

business_unit='srf', channel_id='69e8ac16-4327-4af4-b873-fd5cd6e895a7', character_filter='e'

Input Schema

NameRequiredDescriptionDefault
paramsYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • addedInput schema / $defs / AudioShowsInput
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "business_unit": {
+      "$ref": "#/$defs/BusinessUnit",
+      "description": "SRG SSR Unternehmenseinheit: 'srf', 'rts', 'rsi', 'rtr' oder 'swi'"
+    },
+    "channel_id": {
+      "description": "Radiokanal-ID. Die v2-API listet Radiosendungen nur pro Kanal — gültige IDs liefert srgssr_audio_get_livestreams.",
+      "maxLength": 200,
+      "minLength": 1,
+      "pattern": "^[A-Za-z0-9_-]+$",
+      "title": "Channel Id",
+      "type": "string"
+    },
+    "character_filter": {
+      "anyOf": [
+        {
+          "pattern": "^[a-z#]$",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "description": "Anfangsbuchstabe der Sendungstitel: 'a'–'z' oder '#' für alles Übrige. Weglassen, um alle Buchstaben abzufragen.",
+      "title": "Character Filter"
+    },
+    "page": {
+      "anyOf": [
+        {
+          "minimum": 1,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": 1,
+      "title": "Page"
+    },
+    "page_size": {
+      "anyOf": [
+        {
+          "maximum": 100,
+          "minimum": 1,
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": 20,
+      "title": "Page Size"
+    }
+  },
+  "required": [
+    "business_unit",
+    "channel_id"
+  ],
+  "title": "AudioShowsInput",
+  "type": "object"
+}
    • removedInput schema / $defs / VideoShowsInput
      Removed value: -{
-  "additionalProperties": false,
-  "properties": {
-    "business_unit": {
-      "$ref": "#/$defs/BusinessUnit",
-      "description": "SRG SSR Unternehmenseinheit: 'srf', 'rts', 'rsi', 'rtr' oder 'swi'"
-    },
-    "page": {
-      "anyOf": [
-        {
-          "minimum": 1,
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": 1,
-      "title": "Page"
-    },
-    "page_size": {
-      "anyOf": [
-        {
-          "maximum": 100,
-          "minimum": 1,
-          "type": "integer"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "default": 20,
-      "title": "Page Size"
-    }
-  },
-  "required": [
-    "business_unit"
-  ],
-  "title": "VideoShowsInput",
-  "type": "object"
-}
    • changedInput schema / properties / params / $ref
      Previous value: -"#/$defs/VideoShowsInput"New value: +"#/$defs/AudioShowsInput"
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds useful behavioral context: it explains that shows are grouped by initial letter, and that omitting character_filter triggers multiple queries that are merged. This goes beyond the annotations. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is structured with a main sentence, a use_case block, important_notes, and an example. Each section adds unique value without redundancy. The main sentence is front-loaded. While slightly verbose due to XML tags, the content is purposeful and well-organized.

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 tool has a nested parameter object and an output schema, the description covers the key operational details: required channel_id source, character_filter behavior, and podcast inclusion. Pagination is not explained, but that is a common pattern. The example further clarifies usage. Overall, the description is sufficient for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite the reported schema description coverage of 0%, the nested schema actually contains descriptions for channel_id, business_unit, and character_filter. The tool description reinforces and extends this by explaining the origin of channel_id and the query-count implications of character_filter. It does not detail page/page_size, but these are standard pagination parameters. The description compensates for the schema coverage gap effectively.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Listet Radiosendungen auf') and the resource (SRG SSR radio channel). The use_case provides browsing context, and the title reinforces the purpose. It is distinct from sibling tools like srgssr_audio_get_episodes or srgssr_audio_get_livestreams, though it doesn't explicitly name alternatives.

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 important_notes explicitly state that channel_id is mandatory and must come from srgssr_audio_get_livestreams, and explain the behavior of character_filter (single query vs. 27 combined queries). This gives clear operational guidance. It doesn't explicitly say when not to use this tool, but the use_case implies catalog browsing for radio/podcast formats.

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