CarteleraCines.es

recommend_movies

Read-onlyIdempotent

Recomienda películas basadas en la cartelera real de una ciudad y fechas concretas. Úsala cuando el usuario pida sugerencias o recomendaciones, por ejemplo: - "qué me recomiendas ver este finde" - "qué puedo ver hoy" - "recomiéndame una película en Córdoba"

            Admite filtros como:
            - películas para niños
            - duración máxima
            - puntuación mínima
            - solo estrenos
            - géneros preferidos o a evitar
            - versión (VOSE, doblada...) o franja horaria

            Debe basarse siempre en películas que estén realmente disponibles en cartelera.

Input Schema

TableJSON Schema

Name	Required	Description
`version`	No	Ej: VOSE, Doblada, 3D. Coincidencia parcial.
`con_ninos`	No
`fecha_fin`	No	Opcional. Fecha final YYYY-MM-DD. Si se omite, coincide con fecha_inicio. Máximo 14 días de rango.
`localidad`	Yes	OBLIGATORIO. Ciudad en la que deben existir sesiones reales.
`hora_desde`	No	Hora mínima de la sesión, formato HH:MM.
`hora_hasta`	No	Hora máxima de la sesión, formato HH:MM.
`duracion_max`	No	Duración máxima en minutos.
`fecha_inicio`	No	Opcional. Fecha inicial YYYY-MM-DD. Si se omite, se usa hoy.
`solo_estrenos`	No
`evitar_generos`	No
`min_puntuacion`	No	Puntuación mínima entre 0 y 10.
`generos_preferidos`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedJul 25, 2026
- 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 / localidad / description
```
Added value: +"OBLIGATORIO. Ciudad en la que deben existir sesiones reales."
```
- 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: -[
-  "localidad",
-  "fecha_inicio",
-  "fecha_fin"
-]New value: +[
+  "localidad"
+]
```
First observedJul 24, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds that it uses 'real cartelera' but no additional behavioral traits beyond what annotations provide.

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 well-structured with examples and filter categories, though slightly verbose. It front-loads the main purpose and uses clear Spanish.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema is provided, and the description does not specify the return format. While the tool's purpose is clear, this gap reduces completeness for an AI 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 67%, so baseline 3. Description groups filters (e.g., 'películas para niños' maps to con_ninos) but adds little new 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?

The description clearly states it recommends movies based on real showtimes in a city and dates, with specific example queries that distinguish it from sibling tools like get_cartelera_localidad or 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 provides explicit usage context with example user queries (e.g., 'qué me recomiendas ver este finde') but lacks explicit when-not-to-use or alternative comparisons.

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

All CarteleraCines.es tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?