Skip to main content
Glama

Schedule of Argentine streaming channels

get_schedule
Read-onlyIdempotent

What is on Argentine streaming, radio and TV channels on a given day (today by default): each programme with its start and end time in Buenos Aires, the channel, the hosts and whether it is on air now, with the canonical url of each programme's page on prim.profblu.com. Filter by channel to get one channel's day, or ask only for what is on air now. Answers in the language requested with lang (es, en, it).

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

Input Schema

NameRequiredDescriptionDefault
dateNoDay in Buenos Aires, YYYY-MM-DD, from 7 days ago to 7 days ahead. Defaults to today.
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Defaults to es. Use the language the user writes in.es
limitNoHow many programmes, 1 to 100. Defaults to 40.
channelNoOnly this channel (name or slug).
onAirNowNotrue: only what is on air right now (ignores date).

Output Schema

NameRequiredDescriptionDefault
urlYesThe schedule page on prim.profblu.com
dateYesYYYY-MM-DD in Buenos Aires
langYes
slotsYes
totalYesProgrammes that day (after the channel filter)
timeZoneYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: times are normalized to Buenos Aires, results include a canonical prim.profblu.com URL per programme, and the response language follows the lang parameter rather than the data's native language.

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 first sentence front-loads the core purpose and is followed by two short sentences covering filtering and language. It is dense but every clause carries information; the per-field enumeration of return values is slightly redundant given a structured output schema exists.

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 five optional parameters, an output schema and rich annotations, the definition covers purpose, defaults, timezone, language behavior and the two main query modes. The only material omission is routing guidance relative to who_is_live_now and upcoming_events, which overlap with the on-air and date dimensions.

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 description coverage is 100%, so each parameter is already fully documented including defaults, ranges and the YYYY-MM-DD pattern. The description restates channel filtering and the on-air mode at a high level but adds no syntax, format or edge-case meaning the schema does not already convey, so it sits at the baseline.

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 gives a concrete verb and resource ('What is on Argentine streaming, radio and TV channels on a given day') and enumerates the returned fields (start/end time in Buenos Aires, channel, hosts, on-air status, canonical URL), so an agent knows exactly what this tool produces. It does not explicitly distinguish itself from the sibling who_is_live_now or upcoming_events, which is the only thing keeping it from a 5.

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?

It states clear usage conditions: default is today, use channel to get a single channel's day, use onAirNow to get only what is live, and answers follow the requested lang. It stops short of naming alternatives or exclusions — an agent cannot tell from this text why it would pick get_schedule over who_is_live_now for a live-status question.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources