Skip to main content
Glama

get_cartelera_cine

Read-onlyIdempotent

Obtiene la cartelera real de un cine concreto entre dos fechas. Úsala cuando el usuario mencione un cine específico o quiera saber qué películas hay en un cine determinado, por ejemplo: - "qué ponen en Cinesur Córdoba hoy" - "cartelera de Kinépolis este sábado" - "qué películas hay en ese cine"

            Sirve para obtener todas las películas y sesiones disponibles en ese cine. Admite los mismos
            filtros que get_cartelera_localidad (niños, duración, puntuación, estrenos, géneros, versión, franja horaria).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cineYesOBLIGATORIO. Nombre del cine, por ejemplo "Kinépolis Ciudad de la Imagen".
generosNo
versionNoEj: VOSE, Doblada, 3D. Coincidencia parcial.
con_ninosNo
fecha_finNoOpcional. Fecha final YYYY-MM-DD. Si se omite, coincide con fecha_inicio. Máximo 14 días de rango.
hora_desdeNoHora mínima de la sesión, formato HH:MM.
hora_hastaNoHora máxima de la sesión, formato HH:MM.
duracion_maxNoDuración máxima en minutos.
fecha_inicioNoOpcional. Fecha inicial YYYY-MM-DD. Si se omite, se usa hoy.
solo_estrenosNo
min_puntuacionNoPuntuación mínima entre 0 y 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / cine / description
      Added value: +"OBLIGATORIO. Nombre del cine, por ejemplo \"Kinépolis Ciudad de la Imagen\"."
    • addedInput schema / properties / duracion_max / description
      Added value: +"Duración máxima en minutos."
    • addedInput schema / properties / duracion_max / minimum
      Added value: +1
    • addedInput schema / properties / fecha_fin / description
      Added value: +"Opcional. Fecha final YYYY-MM-DD. Si se omite, coincide con fecha_inicio. Máximo 14 días de rango."
    • addedInput schema / properties / fecha_fin / format
      Added value: +"date"
    • addedInput schema / properties / fecha_inicio / description
      Added value: +"Opcional. Fecha inicial YYYY-MM-DD. Si se omite, se usa hoy."
    • addedInput schema / properties / fecha_inicio / format
      Added value: +"date"
    • addedInput schema / properties / min_puntuacion / description
      Added value: +"Puntuación mínima entre 0 y 10."
    • addedInput schema / properties / min_puntuacion / maximum
      Added value: +10
    • addedInput schema / properties / min_puntuacion / minimum
      Added value: +0
    • changedInput schema / required
      Previous value: -[
      -  "cine",
      -  "fecha_inicio",
      -  "fecha_fin"
      -]New value: +[
      +  "cine"
      +]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool is safe. The description adds context about fetching 'real' showtimes with date range constraints (max 14-day range in parameter schema). No contradictions, but doesn't detail authentication or rate limits.

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 description is concise with two well-structured paragraphs. The first sentence states the core purpose, followed by clear usage examples and a summary of filters. Every sentence contributes meaning, no redundant content.

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?

While lacking an output schema, the description explains it returns 'todas las películas y sesiones disponibles,' which is sufficient for a typical cinema showtime tool. Parameter documentation covers inputs well. Minor gap: no explicit mention of ordering or pagination, but the tool is simple and domain-common.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 73%, so most parameters are already documented. The description adds value by listing the supported filter categories (niños, duración, puntuación, estrenos, géneros, versión, franja horaria) and referring to get_cartelera_localidad for identical filters, helping an agent understand available options.

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 clearly states the tool retrieves ('Obtiene') the real showtimes of a specific cinema between two dates. It distinguishes itself from sibling 'get_cartelera_localidad' by focusing on a single cinema rather than a locality, and provides specific user query examples.

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

Usage Guidelines5/5

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

Explicitly states when to use: when the user mentions a specific cinema or wants to know what movies are playing there. It also implicitly excludes locality-based queries by referencing get_cartelera_localidad as the alternative for that case.

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