Skip to main content
Glama

Search Prim

search
Read-onlyIdempotent

Searches Prim's catalogue of Argentine streaming by name: channels, programmes, people (hosts, streamers, guests) and upcoming events, each with the canonical url of its page on prim.profblu.com. Use it when you only have a name; then get_channel or get_person for the full page. 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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

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 results of each kind, 1 to 10. Defaults to 5.
queryYesWhat to look for, e.g. «Olga», «Nadie dice nada», «Migue Granados».

Output Schema

NameRequiredDescriptionDefault
urlYesThe search page on prim.profblu.com
langYes
queryYes
eventsYes
peopleYes
channelsYes
programsYes

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

A4.1/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 a closed-world catalogue, so the safety profile is covered. The description adds behaviour beyond that: results include canonical page urls, and answers are rendered in the requested language rather than being raw matches.

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, front-loaded with purpose then routing then language behaviour; nothing is padded. The parenthetical (es, en, it) mildly duplicates the schema enum, which is the only waste.

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 and comprehensive annotations, the description need not explain return shape, and it supplies the routing and language information an agent needs to call it correctly. The only shortfall is silence on how results rank or combine across the four entity kinds.

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 per-parameter descriptions and an enum on lang, so the schema already carries the parameter semantics. The description restates lang's enum values and the name-only nature of query but adds no syntax, matching or result-shaping detail beyond the schema.

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?

Specific verb (Searches) plus a precisely scoped resource (Prim's Argentine streaming catalogue by name) and an enumeration of the entity kinds returned: channels, programmes, people, upcoming events. It also states that each hit carries the canonical prim.profblu.com url, which separates it from page-fetching siblings.

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

Usage Guidelines4/5

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

Gives an explicit trigger — 'Use it when you only have a name' — and routes onward to get_channel or get_person for the full page. It does not address other siblings such as get_schedule or upcoming_events, so the alternative coverage is clear but not exhaustive.

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