Skip to main content
Glama

An Argentine streaming channel

get_channel
Read-onlyIdempotent

The page of an Argentine streaming, radio or TV channel on Prim: what it is, where to watch it (YouTube, Twitch, Kick), whether it is live now and with how many viewers, its position in this week's audience ranking, its programmes and its upcoming events, with the canonical url of its page on prim.profblu.com. Accepts the channel's name, slug or Prim url. Answers in the language requested with lang (es, en, it).

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

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
channelYesChannel name, slug or Prim url, e.g. «Luzu TV», luzu-tv or https://prim.profblu.com/c/luzu-tv

Output Schema

NameRequiredDescriptionDefault
urlNoCanonical page of the channel on prim.profblu.com: cite it
kindNomedia (a channel with programmes) or streamer
langYes
nameNo
foundYes
socialNo
countryNo
liveNowNo
websiteNo
programsNoProgrammes on air (current season)
platformsNo
descriptionNo
weeklyRankingNo
upcomingEventsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / upcomingEvents / items / properties / date
      Added value: +{
      +  "description": "Date in Buenos Aires time, YYYY-MM-DD: the one prim.profblu.com shows",
      +  "type": "string"
      +}
    • changedOutput schema / properties / upcomingEvents / items / properties / localDate / description
      Previous value: -"Date where it happens, YYYY-MM-DD"New value: +"Date at the venue, YYYY-MM-DD"
    • changedOutput schema / properties / upcomingEvents / items / properties / localTime / description
      Previous value: -"Time where it happens, HH:MM"New value: +"Start time at the venue's own time zone, HH:MM"
    • addedOutput schema / properties / upcomingEvents / items / properties / time
      Added value: +{
      +  "description": "Start time in Buenos Aires time, HH:MM: the one prim.profblu.com shows",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is well covered. The description adds useful context about what the page returns, including live status, viewer count, ranking, programmes, upcoming events, and canonical URL.

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 single sentence is dense but front-loaded and avoids obvious filler. It could be split for readability, but every clause contributes to understanding the returned page or accepted input.

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?

An output schema exists, so the description need not explain return formatting. Given the modest parameter set, the description covers accepted identifiers, language selection, and page contents adequately, though it could say more about when this lookup is preferred over sibling tools.

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 the schema already documents both parameters in detail. The description restates that channel accepts a name, slug, or Prim URL and that lang controls answer language, but adds no meaningful semantics beyond the schema.

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: retrieving the Prim page for an Argentine streaming, radio, or TV channel. It also enumerates the page contents and accepted input forms, which makes the tool recognizable, though it does not explicitly differentiate it from siblings such as search or who_is_live_now.

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 lookup framing and the accepted channel identifiers, but the description does not state when to use this tool instead of search, who_is_live_now, or other sibling tools. An agent can infer likely use, but no explicit routing guidance is provided.

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