CarteleraCines.es

get_person_movies_in_cartelera

Read-onlyIdempotent

Devuelve TODAS las películas de un actor o director que están en cartelera ahora mismo (con sesiones futuras reales), no solo la más reciente. Úsala cuando el usuario pregunte por la filmografía actual de alguien, por ejemplo: - "qué películas hay de Almodóvar en cartelera" - "qué puedo ver de Cruz en el cine ahora" - "todo lo que hay de Nolan ahora mismo"

            Diferencia con get_latest_movie_by_person: esa tool está pensada para "la última de X" (una sola
            película, priorizando la más reciente aunque no esté en cartel); esta siempre filtra a cartelera
            real y no limita a la más reciente. Útil como base para recomendaciones por gustos de actor/director.

Input Schema

TableJSON Schema

Name	Required	Description
`tipo`	No	Opcional. Por defecto "actor". Usa "director" cuando corresponda.
`persona`	Yes	OBLIGATORIO. Nombre del actor, actriz o director/a.
`localidad`	No

TDQS

A4.7/5.0

Behavior5/5

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

The description details behavioral traits beyond annotations: it filters to real cartelera with future sessions, returns all relevant movies, and is non-destructive. Annotations (readOnlyHint, idempotentHint, destructiveHint) are consistent with the description.

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 well-structured with a clear statement of behavior followed by usage examples and sibling differentiation. It is front-loaded and every sentence adds value without redundancy.

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

Completeness5/5

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

Given no output schema, the description sufficiently explains the return type (list of movies in cartelera) and context. It covers the tool's purpose, usage, and relationship to siblings, making it complete 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 coverage is 67%. The description does not add substantial meaning beyond the schema for the parameters. It mentions default for 'tipo' and requirement for 'persona', but does not elaborate on 'localidad' (which lacks schema description). Baseline 3 is appropriate as schema covers most.

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 returns all movies of a person currently in theaters with future sessions, not just the latest. It uses specific verbs and resources, and explicitly distinguishes from the sibling tool get_latest_movie_by_person.

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?

The description provides explicit usage scenarios with examples, and contrasts with get_latest_movie_by_person, telling the agent when to use this tool vs the alternative. It says 'Úsala cuando...' and explains differences.

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

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

Need Help?