Cinve

Listar sedes

list_cinemas

Read-onlyIdempotent

List cinema venues and their IDs by provider, filtered by city or name, to find locations and retrieve IDs for showtime or price queries.

Instructions

Lista sedes e IDs. Cines Unidos requiere city; Supercines admite city opcional; Cinepic verifica las sedes configuradas Candelaria y VVIP Lido. Los proveedores conservan sedes conocidas sin código verificado (code_status=unverified). Cinex admite city opcional e incluye sedes conocidas ausentes del directorio actual (directory_status=not_listed); ninguna condición indica cierre.

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": "list_cinemas"
  }
}

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.
`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.
`provider`	Yes	Proveedor de cine; obtén capacidades y limitaciones con list_providers.

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.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds real semantic context beyond them: venues may be returned with code_status=unverified, Cinex may include directory_status=not_listed venues, and absence does not imply closure. That last point is a genuinely useful caveat, though caching/refresh implications and result ordering are left unaddressed.

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?

Front-loaded with the core purpose, then provider-specific rules in compact clauses; every sentence carries information. It is dense and jargon-laden (code_status, directory_status) but not padded.

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?

For a six-parameter read tool with an output schema and full annotations, the description supplies the provider-conditional requirement logic and the data-quality caveats an agent needs. Nothing essential to correct invocation is missing.

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 67% and the description adds the crucial meaning the schema cannot express: whether city is mandatory or optional depends on the provider. It adds nothing for limit, offset, query, or refresh, but those are either self-explanatory or already described in 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?

States a specific verb and resource ("Lista sedes e IDs") and then enumerates per-provider behavior, which makes the tool immediately distinguishable from siblings like list_cities or list_movies. An agent knows exactly what it retrieves 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 concrete conditional guidance: Cines Unidos requires city, Supercines and Cinex accept it as optional, Cinepic checks two specific configured venues. It does not name an explicit alternative tool to use instead (e.g. when to prefer list_cities first), which keeps it short of a 5.

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

Deploy Server