Skip to main content
Glama

Cinve

Consultar asientos y mapa ASCII

get_seats
Read-onlyIdempotent

Mapa real sin reservar: Cinex y Cines Unidos requieren cinema_id, session_id y cuenta conectada; Cinepic requiere también movie_id, sin login. Usa IDs de get_showtimes. Devuelve contadores y el mapa ASCII completo, donde cada asiento aparece con su etiqueta y estado (O = status available); include_seats=true añade el detalle por asiento, mucho más extenso. Sin caché local. Para disponibilidad de asientos en Cinex, Cines Unidos y Cinepic, usa get_seats con los IDs verificados de sede y función; Cinepic también requiere movie_id. Muestra el mapa ascii en un bloque de texto monoespaciado con su leyenda y la hora de consulta. Usa solamente status=available de cada asiento para indicar que está libre; conserva occupied, unavailable y unknown por separado. El status=available del resultado significa que se obtuvo un mapa, no que todos sus asientos estén libres ni que la interpretación sea completa. Revisa availability_complete y los contadores: available=0 con unknown>0 NO significa agotado. Si el mapa es parcial, muestra los estados confirmados y los signos ?, explica que Cinve no pudo interpretar parte del mapa y no atribuyas ese fallo al cine ni afirmes que el MCP no soporta asientos. No inventes ubicaciones ni conviertas desconocidos o restringidos en libres. No repitas el login por estados desconocidos: solo ante auth_required. Las consultas no seleccionan ni reservan asientos; la disponibilidad puede cambiar antes de comprar.

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>",
      "cinema_id": "<cinema_id>",
      "session_id": "<session_id>"
    },
    "name": "get_seats"
  }
}

Input Schema

NameRequiredDescriptionDefault
movie_idNoID de película devuelto por list_movies del mismo proveedor; opcional en Cinex cuando se consulta una sede completa.
providerYesProveedor de cine; obtén capacidades y limitaciones con list_providers.
cinema_idYesID 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.
session_idYesID de función devuelto por get_showtimes del mismo proveedor.
include_seatsNotrue: añade seats con id, fila, coordenadas y estado del proveedor de cada asiento. Omítelo para responder sobre disponibilidad: el mapa ascii basta y ocupa una fracción del tamaño.

Output Schema

NameRequiredDescriptionDefault
asciiYes
seatsNoDetalle por asiento; solo con include_seats=true. El mapa ascii ya muestra cada etiqueta con su estado.
totalYes
statusYes
sourcesYes
unknownYes
occupiedYes
providerYes
timezoneYes
warningsYes
availableYes
cinema_idYes
queried_atYes
session_idYes
unavailableYes
availability_completeYesTrue only when a nonempty map has no unknown seat states. Does not promise purchase eligibility or a reservation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses no local caching, that availability can change before purchase, and critically that status=available means a map was obtained rather than that all seats are free. It also explains partial-map handling (availability_complete, counters, unknown>0 not meaning sold out) and instructs not to blame the cinema for unparsed seats. Some of this is restated two or three times, which dilutes rather than extends the disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key facts are front-loaded, but the text repeats the same provider requirements (Cinex/Cines Unidos/Cinepic and movie_id) in two separate sentences and re-explains the status=available caveat several times. Several sentences are operational display instructions that could be compressed into one line, so the block is substantially longer than its information content warrants.

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?

With a full output schema and rich annotations already present, the description fills the remaining gaps an agent needs: partial-map interpretation, the distinction between confirmed, occupied, unavailable and unknown statuses, and the rule not to promote unknowns to free. Edge cases such as available=0 with unknown>0 are addressed, making the definition complete for a read-only, open-world lookup.

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 100%, so baseline would be 3, but the description adds provider-conditional meaning the schema does not make explicit: Cinepic requires movie_id while Cinex may omit it for a full-venue query, and include_seats=true yields a much larger per-seat payload that should be skipped for plain availability answers. It does not add anything about provider enum values or ID format constraints, which the schema already handles.

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 opening line states a specific resource and scope: a real, non-reserving seat map for named providers, with counters plus a full ASCII map. It also names the prerequisite source (IDs from get_showtimes) and the per-provider requirements, so an agent knows exactly what the tool produces and what it does not do (it never selects or reserves seats).

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?

Explicit prerequisites and routing are given: use verified cinema_id and session_id from get_showtimes, Cinepic additionally needs movie_id, and do not re-run login except on auth_required. It also clarifies that queries never select or reserve, implying a separate purchase flow. What is missing is an explicit statement of when to prefer this over adjacent tools such as get_ticket_prices or get_concessions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.