Skip to main content
Glama

A person in Argentine streaming

get_person
Read-onlyIdempotent

The page of a host, streamer, journalist or guest of Argentine streaming on Prim: who they are, what they do, the programmes they are on now (and whether they are on air or when the next show is), their own channel, their social media and their upcoming events, with the canonical url of their page on prim.profblu.com. Accepts the person's name, nickname, 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": {
      "person": "<person>"
    },
    "name": "get_person"
  }
}

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
personYesName, nickname, slug or Prim url, e.g. «Migue Granados», migue or https://prim.profblu.com/p/migue

Output Schema

NameRequiredDescriptionDefault
bioNo
urlNoCanonical page of the person on prim.profblu.com: cite it
langYes
nameNo
foundYes
rolesNoWhat they do: host, streamer, singer, comedian, journalist, columnist, athlete, actor, producer
socialNo
nicknameNo
bioSourceNo
ownChannelNo
upcomingEventsNo
currentProgramsNo

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral substance: the tool answers in the requested language, accepts four different identifier forms, and explicitly reports live/next-show status and the canonical page URL. It omits auth, rate limits, and not-found behavior, keeping it from a 5.

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?

Three sentences, no filler, and the core resource statement is front-loaded before the input-flexibility and language notes. The opening sentence is a long comma-chained enumeration of everything returned, which makes it slightly dense to parse, but every clause conveys 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?

With a full output schema, rich annotations, and 100% parameter coverage, the description needs only to frame what the tool is for and how identifiers are supplied — which it does. The one gap is navigational: it does not tell the agent how this differs from sibling tools that also surface channel, schedule or live data.

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% and both parameters (person, lang) are fully documented in the schema with examples and an enum. The description merely restates the accepted forms and the three language codes, adding no format nuance such as partial-name matching or case sensitivity. Baseline 3 applies.

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 specific resource — the Prim page of an Argentine streaming host, streamer, journalist or guest — and enumerates its contents (current programmes, on-air status, own channel, social media, upcoming events, canonical URL). It is not a verb phrase, but an agent can tell exactly what entity is returned. It never explicitly contrasts itself with siblings like get_channel or upcoming_events, so it stops short of 5.

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 rather than stated: 'use this when you want a person's page' is inferable from the entity description and from the accepted identifier forms (name, nickname, slug, Prim url). There is no when-not guidance and no routing to get_channel, upcoming_events, or who_is_live_now, even though those overlap with data described here (own channel, upcoming events, on-air status).

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