Skip to main content
Glama

Gexiro DACH Pulse & Alexa Voice Suite MCP

get_tv_primetime_lineup

Get live German television broadcasts running right now and tonight at 20:15 CET primetime (Das Erste, ZDF, RTL, ProSieben, SAT.1, VOX, ARTE, 3sat).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_tv_primetime_lineup"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelNoOptional TV channel name (e.g. Das Erste, ZDF, RTL, ProSieben)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It usefully discloses the channel coverage set and the time window (now plus 20:15 CET primetime), but says nothing about return shape, data freshness, behavior for channels outside the listed set, or whether a missing channel yields an empty result or an error.

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?

One front-loaded sentence with zero filler and the scope stated first. It loses a point for mild ambiguity in 'running right now and tonight at 20:15 CET primetime', where it is unclear whether the result is a now-snapshot, the primetime slot, or both combined.

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

Completeness3/5

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

The tool is simple (one optional param, no nested objects, no annotations) and the description covers the domain and time window adequately. However, with no output schema, the description should hint at what a result entry contains (program title, start time, channel) and how the 'now vs. 20:15' scope resolves; that is missing.

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 coverage is 100% and the single optional 'channel' parameter is already documented with examples, so the baseline is 3. The description's channel list reinforces valid values but does not clarify matching rules (exact name vs. fuzzy, what happens on an unlisted or misspelled channel).

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?

States a specific verb ('Get'), resource ('live German television broadcasts'), and an explicit scope ('running right now and tonight at 20:15 CET primetime'), plus the concrete channel roster the data covers. An agent immediately knows this is a TV schedule lookup rather than any of the unrelated German-utility siblings.

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?

Usage is only implied through the temporal framing ('right now and tonight'), which signals when the result is relevant, but there is no explicit when-to-use/when-not statement and no named alternative. Since siblings are unrelated topics, the missing alternatives matter less, but the guidance gap remains.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources