Skip to main content
Glama

CarteleraCines.es

by es.carteleracines

get_latest_movie_by_person

Read-onlyIdempotent

Obtiene la película más reciente asociada a una persona (actor o director). Úsala cuando el usuario pregunte por la última película de alguien, por ejemplo: - "la última de Stallone" - "la última de Scorsese" - "qué es lo último de DiCaprio"

            Opcionalmente puede limitarse a:
            - solo películas actualmente en cartel
            - una ciudad concreta

            Es útil como paso previo para luego buscar dónde ver esa película.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tipoNoOpcional. Usa "director" solo cuando se busque dirección; por defecto se usa "actor".
personaYesOBLIGATORIO. Nombre del actor, actriz o director/a.
localidadNo
solo_en_cartelNo

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to reiterate safety. It adds context about the person type (actor/director) and optional filters, but does not disclose behavior like what happens if the person is not found or if multiple results exist.

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 and well-structured: a single clear sentence defining the tool, followed by example queries and optional filters. No wasted words, and the bullet-like examples aid readability.

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 4 parameters, no output schema, and reasonable complexity, the description covers the core purpose, example queries, and optional filters. It does not explain the return format or error handling, but it is sufficient for the agent to understand the tool's function.

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 50%. The description explains the 'tipo' parameter (use 'director' only when searching for direction) and the required 'persona'. However, 'localidad' and 'solo_en_cartel' are only vaguely mentioned in the usage line, lacking detailed format or constraints 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 the tool obtains the latest movie associated with a person (actor or director), with concrete examples like 'la última de Stallone'. It distinguishes from sibling tools by focusing on a single latest movie rather than a list.

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 when to use the tool (when user asks for the latest movie of someone) and gives examples. It also mentions optional filters (city, currently in theaters). However, it does not explicitly state when NOT to use it or compare to siblings like get_person_movies_in_cartelera.

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