Skip to main content
Glama

Most watched moments of Argentine streaming

top_moments
Read-onlyIdempotent

Today's most watched moments of Argentine streaming (the audience peaks of the day: channel, programme, the minute it happened and how many people were watching, with a link to that minute on prim.profblu.com) and the clips gaining most views right 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": "top_moments"
  }
}

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 peaks and how many clips, 1 to 10. Defaults to 5.

Output Schema

NameRequiredDescriptionDefault
urlYesThe moments page on prim.profblu.com
dateNoDay of the peaks, YYYY-MM-DD in Buenos Aires
langYes
clipsYes
peaksYes
fromYesterdayYestrue when today has no peaks yet and these are yesterday's

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint false, openWorldHint false), so the bar is lower. The description does add useful content-level context — what a 'moment' actually is (channel, programme, minute, viewer count, source link on prim.profblu.com) and that the response language is controllable. It says nothing about data freshness, caching, or empty-result behavior when there are no peaks yet.

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?

One front-loaded sentence states the resource first, then the companion data set, then a compact parenthetical defining the payload. It is dense but every clause carries information; only the trailing lang restatement is redundant with the schema.

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, the description needn't explain return structure, yet it still sketches the payload fields, and read-only safety is handled by annotations. What remains missing is minor: whether the day is timezone-bounded and how the tool relates to the ranking/live siblings.

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 both lang and limit are already documented, and the description merely restates lang with its three enum values. The limit parameter goes entirely unmentioned in the description, and no extra meaning (ordering, tie-breaking, whether peaks and clips share the cap) is added 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 names a concrete resource and scope: today's audience peaks of Argentine streaming plus the clips gaining most views right now, and it enumerates the returned facts (channel, programme, minute, viewer count, link). It is clear enough to separate from a weekly ranking or a live-now check by the 'today's peaks' framing, though it never names a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this tool over weekly_ranking, who_is_live_now, or search; the only usage-like instruction is 'Use the language the user writes in', which is parameter-level, not tool-selection guidance. The 'today's' scope hints at a time frame but leaves the choice between siblings to inference.

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