Skip to main content
Glama
telewebion-mcp

telewebion-mcp

by sepehr071

Telewebion channels

tv_channels
Read-onlyIdempotent

List Telewebion live TV, provincial, and radio channels with the IDs other tools require. Filter by kind and check whether recorded episodes exist.

Instructions

List Telewebion live channels (TV, provincial, radio) with the id the other tools take.

Each row has id (use as channel), Persian name, group and the live page URL. archive false means no recorded episodes exist for that channel.

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

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by group; omit for all 89

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description goes beyond them by disclosing the row shape (id, Persian name, group, live page URL) and explaining that `archive` false means no recorded episodes exist for that channel — non-obvious semantics an agent could not infer from 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?

Two tight sentences with zero filler; the core purpose and id-usage note come first, followed by the row-shape and `archive` semantics. Every clause carries information an agent needs.

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?

No output schema exists, and the description compensates by enumerating the returned fields and explaining the `archive` flag. For a single optional-filter list tool with annotations covering safety, nothing needed to invoke or interpret it 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 enum plus its 'omit for all 89' default is fully documented in the schema. The description's mention of TV/provincial/radio groups loosely maps onto the `kind` values but adds little beyond the enum, so the baseline of 3 applies.

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?

The description opens with a specific verb and resource ('List Telewebion live channels') and scopes it to TV, provincial and radio groups. The clause 'with the id the other tools take' implicitly positions it as the id-resolution entry point relative to its siblings, though it never names them outright.

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?

'with the id the other tools take' tells the agent this is the lookup step that must precede schedule/episode/live tools, which is clear usage context. There is no explicit when-not or named alternative, so it stops short of full routing guidance.

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