Cinve

Consultar caramelería

get_concessions

Read-onlyIdempotent

Retrieve concession menu items and prices for a specific cinema venue by provider and cinema ID, with optional name filtering and pagination.

Instructions

Consulta caramelería por sede. Cinepic y Cines Unidos requieren solo cinema_id, por API pública; Cinepic puede devolver catálogo vacío. Cinex requiere cinema_id y una cuenta conectada. Supercines requiere solo cinema_id. Stock solo cuando está verificado; no usa cero para precios ausentes.

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>"
    },
    "name": "get_concessions"
  }
}

Input Schema

Name	Required	Description
`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.
`cinema_id`	Yes	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

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered; the description adds real behavioral content beyond them — Cinex requires an authenticated account, Cinepic may return an empty catalog, and stock is only surfaced when verified with missing prices not zero-filled. It stops short of covering caching, rate limits or pagination behavior.

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?

The purpose is front-loaded in the first sentence and the rest is densely packed provider-specific caveats with no filler. The telegraphic, fragment-like style is efficient but slightly reduces readability as a cohesive instruction.

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 an output schema present, return-shape explanation is not needed, and the description covers the tricky parts: per-provider auth, empty-catalog possibility and null-price semantics. It is close to complete for a 6-parameter lookup, though it says nothing about limit/offset paging or when refresh is worth using.

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 schema already explains query, refresh, provider and cinema_id. The description adds genuine meaning by declaring which parameters each provider actually requires and that Cinex additionally needs a connected account, information not derivable from the enum alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Consulta caramelería por sede" states a specific verb (consulta) and resource (caramelería) scoped to a cinema location, which separates it cleanly from get_seats, get_showtimes and get_ticket_prices. It does not explicitly contrast itself with any sibling, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives concrete per-provider preconditions (Cinepic/Cines Unidos/Supercines need only cinema_id; Cinex needs a connected account), which tells the agent when a call can succeed. However, there is no when-to-use vs when-not framing or named alternative for the neighbouring tools, so guidance remains implied rather than explicit.

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

Deploy Server