Skip to main content
Glama

Who is live now on Argentine streaming

who_is_live_now
Read-onlyIdempotent

Lists the Argentine streaming, radio and TV channels that are live right now, ordered by concurrent viewers measured by Prim, with the programme on air, the platforms (YouTube, Twitch, Kick) with their watch links and the canonical url of each channel's page on prim.profblu.com. Optionally filter by channel name. 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": "who_is_live_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Defaults to es. Use the language the user writes in.es
limitNoHow many channels, 1 to 50. Defaults to 15.
channelNoOnly this channel (name or slug, e.g. «Luzu TV» or luzu-tv).

Output Schema

NameRequiredDescriptionDefault
urlYesThe «Now» page on prim.profblu.com
langYes
liveYes
notLiveNoOnly when channel names a channel that exists but is not live right now
liveChannelsYesHow many channels are live right now in total
totalViewersYesConcurrent viewers across all of them

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / notLive
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Only when channel names a channel that exists but is not live right now",
      +  "properties": {
      +    "name": {
      +      "type": "string"
      +    },
      +    "nextShow": {
      +      "additionalProperties": false,
      +      "description": "The channel's next programme in Prim's schedule (today or tomorrow, Buenos Aires)",
      +      "properties": {
      +        "program": {
      +          "type": "string"
      +        },
      +        "startsAt": {
      +          "description": "ISO 8601",
      +          "type": "string"
      +        },
      +        "url": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "program",
      +        "startsAt",
      +        "url"
      +      ],
      +      "type": "object"
      +    },
      +    "url": {
      +      "description": "Canonical page of the channel on prim.profblu.com: cite it",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "url"
      +  ],
      +  "type": "object"
      +}
  2. 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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine value beyond that: ranking is by concurrent viewers as measured by Prim, entries include platform watch links across YouTube/Twitch/Kick, and the answer language is selected by the request language. It stops short of stating freshness/caching or how often the live figures update, which matters for a 'right now' tool.

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 core verb and resource are front-loaded in the first clause, and the second sentence covers the optional filter and language. It is dense with enumerated return fields, but every element is informative rather than filler.

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 an output schema present, explaining return fields is technically optional, yet the description summarizes the payload shape helpfully. Three optional parameters are all schema-documented, so nothing essential is missing; only freshness/refresh semantics for a real-time listing remain unstated.

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 each parameter is documented in the schema itself. The description only restates the optional channel-name filter and the language choice, adding no syntax, slug-vs-name disambiguation or default/limit guidance beyond the schema, so the baseline 3 applies.

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 a precisely scoped resource: Argentine streaming, radio and TV channels that are live right now, ordered by concurrent Prim viewers. It also enumerates what each entry carries (programme on air, platforms with watch links, canonical prim.profblu.com url), which separates it clearly from get_channel (single channel) and get_schedule (programming grid).

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?

The description conveys the usage context implicitly through 'live right now' and notes that filtering by channel name is optional, plus a language-selection note. However, it never says when to prefer this over get_channel or get_schedule, nor states any exclusion; the agent must infer the real-time-listing use case.

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