Cinve

Listar sedes

list_cinemas

Read-onlyIdempotent

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 observedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds substantive semantics: known venues are retained with code_status=unverified, Cinex includes venues with directory_status=not_listed, and explicitly "ninguna condición indica cierre" — a crucial caveat preventing an agent from treating a missing code as a closed cinema. It stops short of describing pagination or cache behavior beyond what the schema's refresh field says.

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 compact per-provider clauses; nearly every sentence carries a distinct constraint. The telegraphic style (semicolon-separated clauses) reduces readability slightly but wastes little.

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?

For a multi-provider listing tool with a required enum, conditional city semantics and an output schema, the description covers the risky edge cases (unverified codes, not_listed venues, no closure inference). Pagination via limit/offset is the only notable gap, and defaults/maximums are already in the schema.

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?

The description adds meaning the schema cannot express: city is conditionally required depending on provider, and its value must come from list_cities of the same provider. Schema coverage is 67% and covers city/query/refresh/provider well, but limit and offset remain undocumented in both places, so it does not fully compensate.

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?

"Lista sedes e IDs" gives a specific verb and resource, and the following clauses scope it per provider (Cines Unidos, Supercines, Cinepic, Cinex). It is immediately distinguishable from list_cities/list_movies siblings, and it even names list_cities as the source of valid city values.

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?

Provider-specific rules function as real usage guidance: city is mandatory for Cines Unidos, optional for Supercines and Cinex, and Cinepic is limited to verifying two configured venues. What is missing is an explicit statement of when to prefer this over a sibling such as list_movies or list_cities, though the city-source reference implies the ordering.

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

All Cinve tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.