Skip to main content
Glama

Weekly audience ranking of Argentine streaming

weekly_ranking
Read-onlyIdempotent

This week's audience ranking of Argentine streaming, radio and TV channels, measured by Prim (Monday to Sunday): position, average and peak concurrent viewers, hours live and the movement against last week, with the canonical url of each channel's page on prim.profblu.com. 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": "weekly_ranking"
  }
}

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 positions, 1 to 50. Defaults to 10.

Output Schema

NameRequiredDescriptionDefault
urlYesThe ranking page on prim.profblu.com
langYes
weekEndYes
positionsYes
weekStartYes

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 readOnly, idempotent, non-destructive and closed-world behavior, so the description's contribution is context: the data source (Prim), the Monday-to-Sunday measurement basis, and the exact metrics reported. The only gap is that pagination or freshness of the ranking is not discussed.

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?

A single front-loaded sentence that leads with the ranking and timeframe before enumerating metrics, with no filler sentences. It is dense to the point of being run-on, but every clause carries information.

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 two-parameter read-only tool with an output schema present, the definition covers purpose, data source, measurement period and language handling. It slightly over-specifies the returned fields that the output schema already documents, so it is complete but somewhat redundant.

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% with both parameters fully described, including the enum and default for lang and the 1-50 bound for limit. The description merely restates the lang enum and its purpose, adding no meaning beyond the schema, so the baseline of 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?

The description names a specific verb and resource (weekly audience ranking of Argentine streaming, radio and TV channels) and scopes it to a Monday-to-Sunday measurement window by Prim. An agent can distinguish this from siblings like who_is_live_now or top_moments purely from the text.

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 weekly measurement window and metric set imply when this tool fits, but there is no explicit when-to-use, when-not-to-use, or named alternative for point-in-time or per-channel queries. Usage guidance is inferable rather than stated.

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