Skip to main content
Glama
KiraPC

italian-cinema-mcp

by KiraPC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_showtimes

Query Italian cinema showtimes (UCI, The Space) for a date, with filters for time window, film title, chain, and optional booking links. Returns compact grouped text with format/language tags.

Instructions

Showtimes for the given cinemas on a date, with optional time window and title substring filters. Returns a compact text view grouped by film and cinema: time, and only the format/language tags that deviate from the chain default (2D in Italian -> nothing; e.g. '21:30 IMAX', '20:20 EN', '21:30 ISENSE' otherwise). Italian is the default language and is omitted; EN, OV are normalised. Sold-out shows are tagged '(sold out)'. Booking links stay off by default; pass include_links=true to add them. Pass chain to restrict to one chain or a list (e.g. chain: 'uci' for loyalty promotions); cinema ids that belong to other chains are dropped.

Time axis: each requested date is a 'cinema day' that spans [date 06:00, date+1 06:00) in Europe/Rome. from_time/to_time earlier than 06:00 means the next calendar day (e.g. to_time '01:00' is 'until 01:00+1'). Showtimes after midnight are rendered with a '+1' marker ('22:00+1' is too far east to happen in practice; '00:30+1' is the usual case). If a film has only out-of-window showtimes at a cinema, that cinema line becomes 'cinema - none in window (N earlier, last HH:MM)'; if the film has zero in-window shows anywhere, an 'Outside the time window:' line is appended.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoYYYY-MM-DD in Europe/Rome; defaults to today.
chainNoRestrict the query to one chain or a list of chains. Cinema ids that do not belong to the allowed chain(s) are skipped. Use this for loyalty promotions (e.g. only uci) or to compare apples to apples.
to_timeNoLatest showtime to include (HH:MM).
from_timeNoEarliest showtime to include (HH:MM).
cinema_idsYesCinema ids from list_cinemas.
include_linksNoIf true, append the booking URL inside [brackets] next to each showtime.
title_containsNoCase-insensitive substring the film title must contain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and discloses output format (compact text grouped by film and cinema), default language omission, sold-out tagging, and the time axis convention (06:00 boundary, +1 marker). It also explains out-of-window handling, providing an unusually detailed behavioral contract.

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?

Though lengthy, every sentence adds necessary behavioral detail; the first sentence front-loads the core purpose. The text is structured into general behavior and time-axis specifics without redundancy.

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?

There is no output schema, so the description must explain return values, and it does so exhaustively: formatting, language tags, sold-out marks, links, and edge cases. For a 7-parameter tool with no annotations, this is complete enough to invoke correctly.

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 100%, so the baseline is 3, but the description adds value by explaining the date's 'cinema day' span and the meaning of from_time/to_time earlier than 06:00. It also clarifies chain filtering behavior and include_links default, which the schema only names.

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?

The description begins with 'Showtimes for the given cinemas on a date, with optional time window and title substring filters,' naming the resource and filters. It clearly distinguishes from siblings list_cinemas and list_films by focusing on showtimes for specific cinemas.

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?

The description gives usage context for chain ('Pass chain to restrict to one chain... e.g. chain: 'uci' for loyalty promotions') and include_links ('Booking links stay off by default; pass include_links=true'). It implies the tool is for retrieving showtimes, but it does not explicitly name alternative tools or when not to use it.

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

Deploy Server

Other Tools