Cinve

Consultar caramelería

get_concessions

Read-onlyIdempotent

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

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (readOnly/idempotent/openWorld), it discloses the empty-catalog possibility for Cinepic, the account-connection requirement for Cinex, and the data semantics that stock is only shown when verified and that missing prices are not represented as zero. These are exactly the behavioral caveats an agent needs and cannot get from the annotations or schema.

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 resource statement, then a compact provider-by-provider breakdown with zero filler. The telegraphic final sentence ("Stock solo cuando está verificado") is dense but slightly ambiguous in phrasing.

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 an output schema present, annotations covering safety, and 4 of 6 parameters described in-schema, the remaining burden is provider-specific behavior and data caveats — both of which the description supplies. An agent could call this correctly and interpret empty stock/price results from the description alone.

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 provider-differentiated meaning to provider/cinema_id that the schema only hints at via a pointer to list_providers. It does not address limit/offset/query semantics, leaving some parameters to the schema.

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?

States a specific verb and resource ("Consulta caramelería por sede") plus scope (per-venue). It is clearly a different resource than get_ticket_prices or get_showtimes, though it never names a sibling to route between them explicitly.

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 per-provider prerequisites — Cinepic/Cines Unidos public API with cinema_id only, Cinex needs a connected account, Supercines needs cinema_id only — which is real when/how-to-use guidance. It lacks explicit exclusions (e.g., when to prefer get_ticket_prices over concessions) but the prerequisite matrix is unusually actionable.

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.