Skip to main content
Glama
malkreide

srgssr-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SRG SSR Video – Sendungen auflisten

srgssr_video_get_shows
Read-onlyIdempotent

List TV shows from SRG SSR units (SRF, RTS, RSI, RTR, SWI) with titles, IDs, descriptions. Filter by initial letter for catalog browsing and program analysis.

Instructions

Listet TV-Sendungen einer SRG SSR Unternehmenseinheit auf (SRF, RTS, RSI, RTR, SWI) mit Sendungstitel, ID und Beschreibung.

Katalog-Browsing für TV-Sendungen, Programmanalysen.

Die API gruppiert Sendungen nach Anfangsbuchstabe. Ohne character_filter werden alle Buchstaben abgefragt und zusammengeführt — das sind 27 Abfragen, also nur nutzen, wenn wirklich der ganze Katalog gebraucht wird. Mit character_filter ist es eine einzige Abfrage. page_size gilt pro Buchstabe. Episoden über srgssr_video_get_episodes mit der show_id.

business_unit='srf', character_filter='t'

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / $defs / VideoShowsInput / properties / character_filter
      Added value: +{
+  "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"
+}
  2. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already establish readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: the API groups shows by first letter, omitting character_filter triggers 27 merged queries, and page_size applies per letter. This discloses a significant performance behavior without contradicting any annotation.

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, front-loaded with the verb+resource statement, and efficiently organized into use case, important notes, and example. Every sentence contributes useful information, especially the 27-request warning, with no padding or repetition.

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

Completeness5/5

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

For a list-only tool with annotations and an output schema, the description covers the non-obvious behavior that an agent needs to invoke it correctly: optional letter filtering, per-letter pagination, request-count implications, and the sibling to use for episodes. Nothing essential is missing.

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?

Although schema description coverage is low, the description compensates well for the key parameters: it explains the behavioral impact of character_filter, notes that page_size is per letter, and provides a concrete example with business_unit='srf' and character_filter='t'. It does not add semantic depth for page, but schema defaults and titles cover its basic usage.

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 ('Listet') and resource: TV shows of an SRG SSR business unit, including title, ID, and description. The use case tag ('Katalog-Browsing für TV-Sendungen') makes the tool's role clear and distinguishes it from audio/video siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The important_notes give explicit guidance: without character_filter, 27 requests are executed and should only be made when the whole catalog is truly needed; with character_filter, a single request is made. It also routes episode lookups to srgssr_video_get_episodes via show_id, which is direct when-to-use versus alternative guidance.

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