Skip to main content
Glama
telewebion-mcp

telewebion-mcp

by sepehr071

Telewebion channel schedule

tv_channel_schedule
Read-onlyIdempotent

Retrieves the recorded program log for a TV channel on a given Tehran day, returning start and end times plus episode page URLs, oldest first, so you can see what aired.

Instructions

What aired on a channel on a day, oldest first, with start/end (Tehran time) and episode page URLs.

This is the site's recorded program log, not a forward schedule: Telewebion publishes no future TV guide, and the log trails the broadcast by up to an hour or two. Short clips are left out. Use tv_episode for details.

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

Input Schema

NameRequiredDescriptionDefault
dateNoGregorian YYYY-MM-DD, Tehran day; default today
limitNo
channelYesChannel id from tv_channels, e.g. tv3, varzesh, irinn

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavioral facts: the log trails the broadcast by one to two hours, short clips are omitted, and it is not a future guide. Those are exactly the freshness and coverage caveats an agent cannot derive from structured fields.

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 core answer — channel, day, ordering, timezone, entry contents — is front-loaded in the first sentence. Every following sentence carries a distinct constraint: no future guide, broadcast lag, clips excluded, sibling pointer. No filler or restatement of the tool name.

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?

With no output schema, the description responsibly describes the return shape (ordered entries with start/end and episode URLs) and its freshness limits. The only real omission is any hint about the limit parameter's paging role, which matters for channels with long daily logs.

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 67%, with date (Gregorian YYYY-MM-DD, Tehran day, default today) and channel (id from tv_channels with examples) already documented. The description reinforces the day-scoped semantics and timezone but says nothing about the limit parameter, whose 1–100 / default 40 bounds live only in the schema. Adequate but not compensating for the gap.

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 and resource — what aired on a channel on a given day — plus ordering (oldest first), timezone (Tehran time), and what each entry carries (start/end, episode page URLs). The closing pointer to tv_episode separates it from the per-episode detail tool, so an agent can pick between them without opening schemas.

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?

Explicitly frames this as a recorded log rather than a forward schedule and warns that Telewebion publishes no future guide, which prevents a common mis-invocation. It also routes the agent to tv_episode for details. It stops short of stating positive trigger conditions (e.g., use when reconstructing what already aired), but the negative framing is unusually clear.

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