Cinve

Consultar funciones

get_showtimes

Read-onlyIdempotent

Retrieve Venezuelan cinema showtimes by date, provider, city, or venue, with optional title and movie filters; returns venue, format, pricing IDs, and listing URLs.

Instructions

Consulta funciones de una fecha (hoy en Caracas por defecto). Cinepic requiere cinema_id (123300 Candelaria o 123301 VVIP Lido); Cines Unidos city; Cinex acepta city para todas sus sedes verificadas de la ciudad en una llamada, cinema_id para una sede (con movie_id opcional para filtrar), o solo movie_id para consultar la ficha de la película en todas las sedes; Supercines acepta cinema_id, city o movie_id; Gran Cine (cine de autor, incluye las salas del Paseo Las Mercedes) acepta cinema_id, city o ninguno para todas sus salas, sin IDs de función del proveedor; usa query para filtrar por título. La llamada de sede resuelve títulos contra el catálogo y marca partial cuando no puede confirmar un movie_id. Retorna IDs necesarios para tarifas, sala/formato cuando disponibles y URL de la web.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "provider": "<provider>"
    },
    "name": "get_showtimes"
  }
}

Input Schema

Name	Required	Description
`city`	No	Nombre de ciudad tal como lo devuelve list_cities del mismo proveedor (p. ej. Caracas); no distingue tildes ni mayúsculas en Cines Unidos.
`date`	No	YYYY-MM-DD; por defecto hoy en America/Caracas para películas y funciones de Cinepic/Cines Unidos y funciones de Cinex, Supercines y Gran Cine.
`limit`	No
`query`	No	Filtra por nombre, sin distinguir tildes/mayúsculas.
`offset`	No
`refresh`	No	true: consulta al proveedor sin usar caché local; solicita revalidación HTTP. No garantiza que el proveedor haya actualizado su contenido.
`movie_id`	No	ID de película devuelto por list_movies del mismo proveedor; opcional en Cinex cuando se consulta una sede completa.
`provider`	Yes	Proveedor de cine; obtén capacidades y limitaciones con list_providers.
`cinema_id`	No	ID de sede devuelto por list_cinemas del mismo proveedor. No mezcles IDs entre proveedores. Si la sede incluye code_status, usa cinema_id solo cuando sea verified; los IDs directory-* no permiten consultas.

Output Schema

Name	Required	Description	Default
`items`	Yes
`total`	Yes
`status`	Yes
`partial`	Yes
`sources`	Yes
`provider`	Yes
`timezone`	Yes
`warnings`	Yes
`queried_at`	Yes
`next_offset`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, yet the description adds real behavior: venue queries resolve titles against the catalog and flag `partial` when a movie_id cannot be confirmed, and it names what comes back (IDs for pricing, room/format, web URL). The only omission is that caching/refresh semantics are left to the schema rather than the prose.

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?

Purpose is front-loaded in the first clause, and every following sentence carries provider-specific rules rather than filler. It is a dense run-on sentence, but condensing further would lose the per-provider capability matrix.

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?

With 9 parameters, five providers and an output schema, the description covers the hard parts: required provider IDs, defaults, partial-result marking and return contents. Pagination (limit/offset) is only handled by the schema, a minor residual gap for a tool of this complexity.

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 78%, so the schema carries most definitions, but the description adds meaning the schema cannot express: which parameter combinations are valid for each provider and that `query` filters by title. This is genuine routing semantics beyond the field descriptions.

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?

States a specific verb and resource ("Consulta funciones de una fecha") plus the default scope (hoy en Caracas), and then differentiates the tool's behavior per provider. An agent can tell exactly what this tool returns without opening the schema.

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?

Gives precise per-provider calling rules — Cinepic must use cinema_id, Cines Unidos uses city, Cinex accepts city/cinema_id/movie_id, Gran Cine accepts all or none — which is actionable when-to-use guidance. It does not, however, contrast with siblings like get_ticket_prices or get_seats to say when showtimes versus pricing/seats should be fetched.

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

Deploy Server