Skip to main content
Glama

Upcoming shows of Argentine streaming people

upcoming_events
Read-onlyIdempotent

Upcoming live shows, tours, talks and events of Argentine streaming people and channels, in Argentina and abroad: date and time where it happens, venue, city, line-up and ticket link, with the canonical url of each event's page on prim.profblu.com. Filter by city (e.g. Buenos Aires, Córdoba, Madrid), by dates or by a name in the line-up. 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": "upcoming_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoUntil this day, YYYY-MM-DD (local to the event).
cityNoCity name, e.g. «Buenos Aires», «Rosario», «Montevideo».
fromNoFrom this day, YYYY-MM-DD (local to the event).
langNoLanguage of the answer: es (Spanish), en (English) or it (Italian). Defaults to es. Use the language the user writes in.es
limitNoHow many events, 1 to 25. Defaults to 10.
queryNoA name in the line-up or in the title, e.g. «Nadie Dice Nada».

Output Schema

NameRequiredDescriptionDefault
urlYesThe events page on prim.profblu.com
cityNo
langYes
totalYesUpcoming events matching the filters
eventsYes
citiesWithEventsNoOnly when the city asked for has no upcoming events

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / events / 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 / events / 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 / events / 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 / events / 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.8/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 safety profile is covered. The description adds genuine context beyond that: the geographic scope (Argentina and abroad), the exact shape of what comes back including the canonical prim.profblu.com URL, and the response-language behavior driven by lang.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is front-loaded with the resource and scope, then moves to filters, then to language handling, with no filler sentences. Despite being one dense passage, every clause contributes either scope, return shape, or filtering 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?

All six parameters are optional and fully documented in the schema, and an output schema exists, so the description does not need to explain return serialization. It covers scope, filters and language adequately; the only gap is that it never situates the tool relative to the other retrieval 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 every parameter already carries its own documentation and examples, including the date patterns and the lang enum. The description restates the same filters (city, dates, line-up name, lang) without adding format or edge-case semantics, so it does not exceed the baseline for a fully documented 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 (upcoming live shows, tours, talks and events of Argentine streaming people) and enumerates the returned fields (date/time, venue, city, line-up, ticket link, canonical URL). That is far more specific than the title alone, but it never distinguishes this from adjacent siblings such as get_schedule or who_is_live_now, leaving the agent to infer the boundary.

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?

It states which filters are available (city, dates, a name in the line-up) and that answers follow the lang parameter, which implies how to narrow a query. However, it gives no explicit when-to-use versus when-not-to-use guidance and no mention of the sibling tools that cover related needs, so usage is only implied.

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