Skip to main content
Glama

tabii_live_channels

Lists the 15 live TRT channels with IDs, titles, slugs, watch links, and public HLS stream URLs, optionally in Turkish, English, Spanish, Arabic, or Urdu for catalog lookup.

Instructions

The 15 live TRT channels on tabii (TRT 1, TRT 2, TRT Belgesel, TRT Haber, TRT Spor, TRT Çocuk, TRT World, ...), each with id, title, slug, watch URL and the public HLS stream URL. language: "tr" (default), "en", "es", "ar" or "ur". No arguments besides language. Note: the streams are the site's public HLS URLs; actual playback may still need a tabii login for some channels.

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": "tabii_live_channels"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNotr

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the burden and does reasonably well: it discloses that the HLS URLs are public site URLs but that actual playback may still require a tabii login for some channels — a caveat an agent could not infer from the schema. It does not address whether the listing is static or reflects live status, but the critical gotcha for downstream use is surfaced.

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-loaded with the resource and its scope, then the parameter values, then a caveat — good ordering with little waste. Minor deduction for awkward line breaks splitting sentences and an open-ended channel list ending in "..." that pads rather than informs.

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?

An output schema exists, so return-value explanation is optional, yet the description still sketches the payload, which helps. For a single-optional-parameter read tool this is close to complete; the only soft spot is not saying whether the channel set or stream URLs change over time.

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

Parameters5/5

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

Schema coverage is 0% and the schema has no enum, yet the description supplies the full accepted value set for language (tr default, en, es, ar, ur). That is exactly the semantic information missing from the structured field, and it removes any guesswork about valid inputs.

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 resource (the 15 live TRT channels on tabii), names concrete examples (TRT 1, TRT World, TRT Çocuk), and enumerates the returned fields (id, title, slug, watch URL, HLS stream URL). This is unmistakably distinct from siblings like tabii_get_show or tabii_search_content, which operate on individual shows or queries.

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?

"No arguments besides language" implies you call it bare to enumerate the full lineup, but there is no explicit when-to-use framing (e.g. use this instead of searching when you want the complete live lineup) nor any when-not-to-use exclusion. The login caveat is a playback note, not selection guidance.

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