Skip to main content
Glama
telewebion-mcp

telewebion-mcp

by sepehr071

Telewebion live sports

tv_live_events
Read-onlyIdempotent

List sports broadcasts scheduled or live on Telewebion for a given date, including league, stage, Tehran times, and page URLs.

Instructions

List sports broadcasts (football, volleyball, ...) scheduled or live on Telewebion that day, with page URLs.

Times are Tehran time (converted from the feed's real UTC). league is the competition, stage the round.

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

Input Schema

NameRequiredDescriptionDefault
dateNoGregorian YYYY-MM-DD; default today

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?

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious context the annotations cannot: times are Tehran local converted from the feed's UTC, and results include page URLs. It stops short of saying how many events come back or how sparse days behave.

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?

Two sentences, front-loaded with the core capability and scope, with no filler. The trailing field-gloss is compact and earns its space, though it slightly blurs input versus output concerns.

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?

For a one-parameter read tool with no output schema and rich annotations, this is close to complete: it covers scope, timezone handling, and the shape of returned fields. Missing only volume/pagination expectations and whether non-sports or off-season days return empty results.

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 `date` parameter is fully documented in the schema, including the Gregorian format and today-default, so the baseline is 3. The description's field notes (`league` as competition, `stage` as round) describe result fields rather than adding meaning to the input parameter.

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?

States a specific verb (List) and resource (sports broadcasts on Telewebion), plus scope (scheduled or live that day) and content (page URLs). It implicitly separates itself from tv_live_now by being sports-only and day-scoped, but never names an alternative, so the differentiation is inferential rather than explicit.

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 implied by the scope phrase 'scheduled or live ... that day' — an agent can infer this is for sports fixtures on a given date. There is no explicit when-not guidance or routing to siblings such as tv_live_now for non-sports live content, leaving the choice to inference.

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