SceneF — California, Florida and Hawaii Movie Showtimes

Discount grid

scenef_discounts

Read-onlyIdempotent

Every structured discount across one board's theaters — venue, label, detail, and day-bound days — with the ones that apply today flagged. Membership and discount-card pricing is not listed; it reads "Member pricing; see the theater". Read-only: the call itself records nothing.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`region`	No	Which regional board to read: a board id such as "sf", "oahu" or "miami", not a city name ("Honolulu" or "Chicago" is rejected). Omitted means "sf" (San Francisco); it is never inferred from where you are. For a city, ZIP or neighborhood call scenef_resolve_board first; scenef_now with no region lists every id. An unknown region is an error, not a fallback.
`response_format`	No	Output size. "concise" (default) is tight text plus a structured summary. In whats_playing, each film has the total showtime_count, next_showtime, and a showtimes array containing only that next screening; "detailed" adds showtime rows with ids, ticket urls and accuracy metadata, about 200 across the answer. film_details and search_showtimes return the 40 nearest showtimes in "concise" and up to 200 in "detailed". showtime_count is always the total and showtimes_complete says whether the array is all of it; narrow by date or theater for the rest.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`region`	Yes
`venues`	Yes
`timezone`	Yes
`today_dow`	Yes
`data_as_of`	Yes
`today_name`	Yes
`attribution`	Yes
`region_name`	Yes
`accuracy_url`	Yes
`applies_today_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 2, 2026

changedInput schema / properties / region / description

Previous value: -"Which regional board to read, e.g. \"sf\", \"oahu\", \"sacramento\". Omitted means the default board — it is never inferred from where you are. Call scenef_now for the full list; an unknown region is an error, not a fallback."New value: +"Which regional board to read: a board id such as \"sf\", \"oahu\" or \"miami\", not a city name (\"Honolulu\" or \"Chicago\" is rejected). Omitted means \"sf\" (San Francisco); it is never inferred from where you are. For a city, ZIP or neighborhood call scenef_resolve_board first; scenef_now with no region lists every id. An unknown region is an error, not a fallback."

addedInput schema / properties / region / maxLength
```
Added value: +120
```

changedInput schema / properties / response_format / description

Previous value: -"Output size. \"concise\" (default) is tight text plus a structured summary. In whats_playing, each film has the total showtime_count, next_showtime, and a showtimes array containing only that next screening; showtimes_complete says whether the array is exhaustive. \"detailed\" includes all selected showtime rows with ids, ticket urls, and accuracy metadata. Use scenef_search_showtimes for all times for one film or theatre."New value: +"Output size. \"concise\" (default) is tight text plus a structured summary. In whats_playing, each film has the total showtime_count, next_showtime, and a showtimes array containing only that next screening; \"detailed\" adds showtime rows with ids, ticket urls and accuracy metadata, about 200 across the answer. film_details and search_showtimes return the 40 nearest showtimes in \"concise\" and up to 200 in \"detailed\". showtime_count is always the total and showtimes_complete says whether the array is all of it; narrow by date or theater for the rest."

Changed1 schema field changedSep 18, 2026

changedInput schema / properties / response_format / description

Previous value: -"Output size. \"concise\" (default) is tight text plus a structured summary — on list-shaped tools each film carries showtime_count and next_showtime, but NOT the full showtimes array. \"detailed\" adds the per-showtime rows with ids, ticket urls, and accuracy metadata. Concise measures ~10KB where detailed measures ~69KB, so ask for detailed when you need the rows and scenef_search_showtimes when you need them for one film or theatre."New value: +"Output size. \"concise\" (default) is tight text plus a structured summary. In whats_playing, each film has the total showtime_count, next_showtime, and a showtimes array containing only that next screening; showtimes_complete says whether the array is exhaustive. \"detailed\" includes all selected showtime rows with ids, ticket urls, and accuracy metadata. Use scenef_search_showtimes for all times for one film or theatre."

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / response_format / description

Previous value: -"Output size: \"concise\" (default) for tight text lines, \"detailed\" to add ids, per-showtime ticket urls, and extra metadata."New value: +"Output size. \"concise\" (default) is tight text plus a structured summary — on list-shaped tools each film carries showtime_count and next_showtime, but NOT the full showtimes array. \"detailed\" adds the per-showtime rows with ids, ticket urls, and accuracy metadata. Concise measures ~10KB where detailed measures ~69KB, so ask for detailed when you need the rows and scenef_search_showtimes when you need them for one film or theatre."

Changed5 schema fields changedSep 6, 2026

addedInput schema / properties / region

Added value: +{
+  "description": "Which regional board to read, e.g. \"sf\", \"oahu\", \"sacramento\". Omitted means the default board — it is never inferred from where you are. Call scenef_now for the full list; an unknown region is an error, not a fallback.",
+  "type": "string"
+}

addedOutput schema / properties / region
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / region_name
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / timezone
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "data_as_of",
-  "attribution",
-  "accuracy_url",
-  "today_dow",
-  "today_name",
-  "applies_today_count",
-  "venues"
-]New value: +[
+  "data_as_of",
+  "attribution",
+  "accuracy_url",
+  "region",
+  "region_name",
+  "timezone",
+  "today_dow",
+  "today_name",
+  "applies_today_count",
+  "venues"
+]

Changed1 schema field changedAug 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": false,
+  "properties": {
+    "accuracy_url": {
+      "type": "string"
+    },
+    "applies_today_count": {
+      "type": "number"
+    },
+    "attribution": {
+      "type": "string"
+    },
+    "data_as_of": {
+      "type": "string"
+    },
+    "today_dow": {
+      "type": "number"
+    },
+    "today_name": {
+      "type": "string"
+    },
+    "venues": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "discounts": {
+            "items": {
+              "additionalProperties": {},
+              "properties": {
+                "applies_today": {
+                  "type": "boolean"
+                },
+                "day": {
+                  "anyOf": [
+                    {
+                      "type": "number"
+                    },
+                    {
+                      "type": "null"
+                    }
+                  ]
+                },
+                "detail": {
+                  "type": "string"
+                },
+                "kind": {
+                  "type": "string"
+                },
+                "label": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "label",
+                "kind",
+                "day",
+                "detail",
+                "applies_today"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          },
+          "neighborhood": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "short": {
+            "type": "string"
+          },
+          "venue_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "venue_id",
+          "name",
+          "short",
+          "neighborhood",
+          "discounts"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "data_as_of",
+    "attribution",
+    "accuracy_url",
+    "today_dow",
+    "today_name",
+    "applies_today_count",
+    "venues"
+  ],
+  "type": "object"
+}

First observedAug 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/destructive=false, so the 'Read-only: the call itself records nothing' line is redundant. The genuine value-add is the disclosure that membership and discount-card pricing is deliberately excluded and surfaces as 'Member pricing; see the theater' — a real limitation an agent could not derive from structured fields.

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 and returned fields, then the exclusion, then the read-only note. Mostly earns its space, though the trailing read-only clause restates annotations and could be cut.

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 annotations covering safety, a 100%-covered two-param schema, and an output schema handling return structure, the description is complete enough. The one notable gap is that it neither references scenef_resolve_board (required for city/ZIP input, per the schema) nor clarifies what 'structured' discounts exclude beyond membership pricing.

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 description coverage is 100%, so the region and response_format semantics (board id vs city, default 'sf', enum sizing) are fully documented in the schema. The description adds no parameter detail beyond that, which is the expected baseline when the schema does the work.

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?

The description states a specific resource and scope: 'Every structured discount across one board's theaters,' then enumerates the returned fields (venue, label, detail, day-bound days). It is clearly distinguishable from siblings like scenef_whats_playing or scenef_theater_info, though it never names an alternative to contrast with.

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?

Usage is implied — call this to see discounts for a board — but there is no explicit when-to-use, when-not-to-use, or pointer to a preferred sibling. An agent can infer intent but receives no routing guidance.

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

All SceneF — California, Florida and Hawaii Movie Showtimes 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.

Resources

Need Help?