Skip to main content
Glama
malkreide

srgssr-mcp

by malkreide
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

SRG SSR EPG – Programmvorschau

srgssr_epg_get_programs
Read-onlyIdempotent

Retrieve the full TV or radio program schedule for SRG SSR channels on a specific date. Use it to get program previews and editorial tips for SRF, RTS, or RSI.

Instructions

Ruft den vollständigen Programmplan (Electronic Program Guide) eines SRG SSR TV- oder Radiosenders für einen bestimmten Tag ab.

TV-/Radio-Programmvorschauen, redaktionelle Programm-Tipps.

Verfügbar nur für SRF, RTS und RSI — nicht für RTR oder SWI. Die channel_id ist eine Sender-Kennung der EPG-API und wird mit Bindestrich geschrieben ('srf-1', nicht 'srf1'); RTS-Radio verwendet Grossbuchstaben. Bekannte Sender: srf tv: srf-1, srf-2, srf-info srf radio: srf-1, srf-2, srf-2-kultur, srf-3, srf-4, srf-musikwelle, srf-virus rts tv: rts-1, rts-2, rts-info rts radio: LA1ERE, ESPACE2, COULEUR3, OPTION_MUSIQUE rsi tv: la-1, la-2 rsi radio: rete-uno, rete-due, rete-tre

business_unit='srf', broadcast_type='tv', channel_id='srf-1', date='2026-04-30'

business_unit='rsi', broadcast_type='radio', channel_id='rete-uno', date='2026-04-30'

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 / EpgProgramsInput / properties / broadcast_type
      Added value: +{
+  "default": "tv",
+  "description": "Sendertyp: 'tv' oder 'radio'",
+  "pattern": "^(tv|radio)$",
+  "title": "Broadcast Type",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already mark this as read-only, idempotent, and non-destructive, so the bar for behavioral disclosure is lower. The description adds valuable behavioral context: the channel_id naming convention, uppercase requirements for RTS radio, and the specific availability limitations. It does not contradict the annotations.

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 front-loaded with the core purpose and then structured into use case, important notes, and examples. The channel list is long but earns its place because it prevents likely mistakes with channel_id formatting and availability.

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?

Given the simple parameter objectabbility and the presence of an output schema, this description is complete enough for an agent to invoke the tool correctly. It covers what the tool does, which business units and channels are valid, formatting quirks, and concrete usage examples. No critical information 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?

Schema description coverage is low, but the description compensates by explaining the channel_id format, listing many valid channel IDs, and providing two worked examples that map business_unit, broadcast_type, channel_id, and date. It does not deeply define `date` beyond the schema pattern, but the examples and opening sentence supply sufficient semantics.

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 action—retrieving the full electronic program guide for an SRG SSR TV or radio channel for a given day—with clear scope. It identifies the resource (program schedule) and is distinguishable from all sibling tools, which focus on weather, audio/video episodes, or polis data.

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 description gives clear context: TV/radio program previews and editorial program tips. It also provides explicit exclusions ('nicht für RTR oder SWI') and known channels, but it does not explicitly name alternative tools or when to prefer them over this one.

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