Skip to main content
Glama

Consultar tarifas

get_ticket_prices
Read-onlyIdempotent

Queries ticket prices for a specific cinema session using provider, cinema and session IDs, returning USD/VES rates when verifiable.

Instructions

Consulta tarifas (Gran Cine no las publica). Cinepic requiere cinema_id, movie_id y session_id de get_showtimes. Cines Unidos requiere cinema_id, session_id y una cuenta conectada. Cinex requiere cinema_id, session_id y una cuenta conectada. Supercines requiere cinema_id, movie_id y session_id, y date si la función no es de hoy; no requiere cuenta (si el usuario conectó la suya, se leen con ella). Devuelve USD/VES cuando verificables, desglose Cinex en VES. No devuelve totales finales de compra.

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_ticket_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoSolo Supercines: fecha de la función (YYYY-MM-DD), la misma usada en get_showtimes; por defecto hoy en America/Caracas. Sus tarifas varían por día.
limitNo
offsetNo
refreshNotrue: consulta al proveedor sin usar caché local; solicita revalidación HTTP. No garantiza que el proveedor haya actualizado su contenido.
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.

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYes
statusYes
partialYes
sourcesYes
providerYes
timezoneYes
warningsYes
queried_atYes
next_offsetYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, and the description adds real behavioral context on top: an auth/connected-account requirement for Cines Unidos and Cinex, an optional-account path for Supercines, the date-sensitivity of Supercines fares, and the caveat that final purchase totals are not returned. Caching/refresh behavior is left entirely to the schema, which is a modest gap.

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

Conciseness5/5

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

One compact provider-per-clause structure, front-loaded with the tool's purpose and the Gran Cine exclusion, then requirements, then return semantics. No sentence is decorative or repeated.

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 an 8-parameter, five-provider tool with conditional requirements, the description covers prerequisites, account needs, provider exceptions, and return-value limits. The output schema carries the return shape, so nothing an agent needs to invoke this correctly 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?

The description supplies conditional-required semantics the schema cannot express: movie_id required for Cinepic and Supercines but optional for Cinex, date only meaningful for Supercines, and the account dependency per provider. limit/offset/refresh are not discussed in the description, though the schema documents them at 75% coverage.

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 (fetch ticket prices) and immediately scopes it by provider, including the exclusion that Gran Cine publishes none. An agent knows exactly what this returns and which providers it covers 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 per-provider preconditions (which IDs each chain needs, which require a connected account) and routes the agent to get_showtimes for session_id. It does not name an alternative tool for the same data nor state general when-not-to-call conditions beyond the Gran Cine exclusion.

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