Skip to main content
Glama

Render an interactive seat map widget

render_seat_map_html

Render a fully interactive HTML seat map showing real-time seat availability for a movie at a Cineplex theatre. Includes showtime picker, zoomable auditorium, and filters to avoid front rows, side seats, or find contiguous seats.

Instructions

Given a movie title, theatre, and date, returns a complete, self-contained, already-tested HTML page that visualizes real seat availability: theatre header, a showtime picker, a pannable/zoomable auditorium seat map, live front-row/side/min-together filter controls, and a stats strip. IMPORTANT: render the returned HTML inline in the chat as a widget (via the Visualizer's show_widget / widget_code) exactly as given — never save it to a file, publish it as a hosted artifact, or open it in a browser. Do not rewrite, regenerate, paraphrase, or modify the code in any way, just pass it through verbatim. Pass theatreName/theatreAddress/distanceKm through from a prior find_theatres result if you have them, to avoid an extra lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesDate in YYYY-MM-DD format
theatreIdYesCineplex theatre ID, from find_theatres
distanceKmNoTheatre distance in km, e.g. from find_theatres
movieTitleYesMovie title, e.g. 'The Odyssey'
formatMatchNoCase-insensitive substring to match against the showtime's format/experience tag, default 'IMAX'
theatreNameNoTheatre display name, e.g. from find_theatres — defaults to 'Theatre {id}' if omitted
minContiguousNoMinimum contiguous open seats required in the initial view, default 1 (its no-op value)
theatreAddressNoTheatre street address, e.g. from find_theatres
excludeFrontRowsNoFront rows to exclude in the initial view, default 0 (widget opens unfiltered; the user can adjust it live)
excludeSideSeatsNoSeats to exclude from each side wall in the initial view, default 0 (widget opens unfiltered; the user can adjust it live)
Behavior4/5

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

No annotations provided, so description must disclose behavior. It explains the HTML content and constraints (inline rendering, no modification). However, it lacks details on failure modes or data freshness. Overall, it provides key behavioral context.

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 description is a single paragraph but front-loads the core purpose. Every sentence adds value, though it could be more structured. It is concise enough for the complexity involved.

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?

Given 10 parameters and no output schema, the description covers output format (HTML widget), usage constraints, and parameter hints. It lacks error handling details, but overall provides a solid understanding of the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so description adds limited semantic value. It mentions passing theatreName/theatreAddress/distanceKm from prior results, which adds usage context, but does not elaborate on parameter meanings beyond schema.

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 clearly states the tool returns an HTML page visualizing seat availability, specifying the inputs (movie, theatre, date) and the output (self-contained widget). It distinguishes from siblings like find_theatres or find_movie by focusing on rendering a visual widget.

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

Usage Guidelines5/5

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

Explicit instructions are given: render inline via show_widget, never save to file, do not modify code. Also advises passing theatreName/theatreAddress/distanceKm from find_theatres to avoid extra lookups. This clarifies when and how to use the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yinbri/cineplex-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server