Skip to main content
Glama

CarteleraCines.es

by es.carteleracines

get_cartelera_localidad

Read-onlyIdempotent

Obtiene la cartelera real de una ciudad entre dos fechas. Úsala cuando el usuario quiera saber qué películas están disponibles en una localidad, por ejemplo: - "qué ponen hoy en Córdoba" - "qué puedo ver este fin de semana en Sevilla" - "qué hay en cartelera mañana en Málaga"

            También permite filtrar resultados según:
            - películas aptas para niños
            - duración máxima
            - puntuación mínima
            - solo estrenos
            - géneros específicos
            - versión (VOSE, doblada...) o franja horaria (hora_desde/hora_hasta)

            Si el usuario pide recomendaciones generales en una ciudad, puedes usar esta tool como base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
localidadYesOBLIGATORIO. Nombre de la ciudad, por ejemplo "Córdoba".
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.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds behavioral context: it returns 'cartelera real', emphasizes the date range, and lists possible filters. No contradictions with annotations. It does not detail rate limits or auth, but annotations suffice.

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?

The description is front-loaded with the main purpose, then examples, then filtering options. It is slightly lengthy but every sentence adds value. Could be more structured (e.g., bullet lists) but is clear and well-organized.

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?

Given the complexity (11 parameters, no output schema), the description covers purpose, examples, and filtering options adequately. It does not explain the return format or error handling, but for a query tool with good annotations, the description is fairly complete and actionable for an agent.

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 73%, so the schema already documents most parameters. The description lists available filters like 'con_ninos', 'duracion_max', etc., but does not add new semantic details beyond the schema. This matches the baseline of 3 for a tool with high schema coverage.

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 states 'Obtiene la cartelera real de una ciudad entre dos fechas', a specific verb and resource. It provides concrete examples (e.g., 'qué ponen hoy en Córdoba') and lists filtering options, making it easy for an agent to understand exactly what this tool retrieves. It clearly distinguishes from siblings like 'get_cartelera_cine' (per-cinema) and 'find_movie_showtimes'.

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?

The description explicitly says 'Úsala cuando el usuario quiera saber qué películas están disponibles en una localidad' and provides multiple query examples. It does not explicitly state when not to use or name alternative tools, but the context of sibling tools is available, and the examples provide strong usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All CarteleraCines.es toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: find_movie for fuzzy title search, find_movie_showtimes for specific movie showtimes, find_nearby_cines for nearby cinemas, etc. Overlaps are minimal and descriptions clarify boundaries.

Naming Consistency5/5

All tool names follow a consistent 'verb_noun' pattern with underscores and lowercase (e.g., find_movie, get_cartelera_cine, where_to_watch_online). No mixed conventions.

Tool Count5/5

11 tools cover the domain of a cinema information server without being overwhelming or insufficient. Each tool addresses a specific user need (search, showtimes, recommendations, streaming).

Completeness4/5

The tool set covers major user intents: finding movies, showtimes, cinemas, details, recommendations, and streaming availability. Minor gap: no tool for cinema amenities or user reviews, but core workflows are covered.

Resources