Skip to main content
Glama

mediathek_by_channel

Retrieve recent programmes from a specified German Mediathek channel, ordered newest first, with an optional result limit.

Instructions

Newest programmes of one channel, newest first. channel: e.g. "ZDF", "ARD", "3sat", "ARTE.DE", "PHOENIX" (see mediathek_list_channels). limit: 1..50 (default 10).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "channel": "<channel>"
    },
    "name": "mediathek_by_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
channelYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden. It discloses the ordering guarantee ('newest first') and the limit's default, which is real value, but says nothing about error handling for an invalid channel or whether results are capped beyond limit.

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?

Front-loads purpose and ordering, then documents each parameter in a compact parenthetical. Dense but readable; no filler sentences.

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?

For a two-parameter read tool with an output schema, the description covers purpose, ordering, valid channel values, and the limit range. The only meaningful gap is failure behavior for unknown channels.

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 coverage is 0%, so the description must compensate, and it does for both parameters: concrete channel examples plus a pointer to mediathek_list_channels, and the limit range 1..50 with default 10. Format details (case sensitivity, exact identifier form) are still left open.

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?

States a specific resource and scope: 'Newest programmes of one channel, newest first.' The channel restriction implicitly distinguishes it from mediathek_by_topic and mediathek_search_programmes, but no sibling is named explicitly.

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

Usage Guidelines3/5

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

Implies usage (browse a channel's newest items) and helpfully redirects to mediathek_list_channels for valid channel names. It gives no explicit when-to-use/when-not guidance versus topic browsing or searching.

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