Skip to main content
Glama
telewebion-mcp

telewebion-mcp

by sepehr071

Telewebion live now

tv_live_now
Read-onlyIdempotent

Lists recent logged programs for each channel in a selected group, defaulting to national TV, and returns live page URLs. Open a URL to watch the broadcast.

Instructions

Show the most recent program on each channel of a group (national TV by default), with live page URLs.

"Most recent" is the newest logged episode of today, which can trail the live broadcast by up to an hour or two. Open live_url to actually watch.

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_live_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoChannel group to scannational
channelsNoSpecific channel ids instead of a group

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, idempotent, open-world tool. The description adds genuinely useful behavior beyond that: it warns that the 'most recent' episode can lag the live broadcast by up to an hour or two, and it tells the agent to open live_url to actually watch. That is exactly the kind of caveat an agent would otherwise get wrong; only the absence of detail on result paging or ordering across channels keeps it from a 5.

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?

The description is two short, front-loaded parts: what it returns, then the important caveat about lag with a pointer to live_url. Every sentence carries useful information. A slightly tighter phrasing could have merged them, but there is no padding.

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?

There is no output schema, so the description takes on the job of naming the key return field, live_url, and it does. Together with the lag caveat, that covers what an agent needs to call the tool and interpret the result. Minor gaps include the ordering or grouping of channels in the response and the nullability behavior of channels, which is left to the schema.

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 and both parameter descriptions are fully documented in the schema, so the baseline is 3. The description reinforces the default group and implies that selection is list-based, but it says nothing about how the channels list interacts with kind or what id format is expected. It adds little beyond the schema, which is acceptable here.

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 states a specific verb and resource: it shows the most recent program for each channel in a group and includes live page URLs, with a sensible default of national TV. It does not explicitly contrast itself with siblings such as tv_channel_schedule or tv_live_events, so an agent must infer the difference. Even so, 'most recent program per channel with live URLs' is concrete enough to act on.

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: this is the tool to use when you want a quick snapshot of what is on across channels, or when you want a direct watch link. It offers no explicit when-not-to-use guidance and does not point to alternatives for schedules or per-episode detail. The default group is stated, but guidance on when to pass channels instead is missing.

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