SceneF — California, Florida and Hawaii Movie Showtimes

Coming soon (on-sale radar)

scenef_coming_soon

Read-only

Films whose first screening on this board is more than 48 hours out, sorted by first night — the on-sale radar for runs worth booking early. Configurable horizon. Every emitted showtime carries confidence, source tier, reporting sources and verified_at. In whats_playing, "concise" gives the total showtime_count and one next screening in showtimes; showtimes_complete identifies a partial array. "detailed" includes the full array.

Input Schema

TableJSON Schema

Name	Required	Description
`region`	No	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.
`horizon_days`	No	How far ahead to look (default 21 days).
`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; 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.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`films`	Yes
`region`	Yes
`timezone`	Yes
`data_as_of`	Yes
`film_count`	Yes
`attribution`	Yes
`region_name`	Yes
`accuracy_url`	Yes
`horizon_days`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

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",
-  "horizon_days",
-  "film_count",
-  "films"
-]New value: +[
+  "data_as_of",
+  "attribution",
+  "accuracy_url",
+  "region",
+  "region_name",
+  "timezone",
+  "horizon_days",
+  "film_count",
+  "films"
+]

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"
+    },
+    "attribution": {
+      "type": "string"
+    },
+    "data_as_of": {
+      "type": "string"
+    },
+    "film_count": {
+      "type": "number"
+    },
+    "films": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "directors": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "first_night": {
+            "type": "string"
+          },
+          "genres": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "key": {
+            "type": "string"
+          },
+          "opening_venues": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "runtime_min": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "slug": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          },
+          "year": {
+            "anyOf": [
+              {
+                "type": "number"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          }
+        },
+        "required": [
+          "key",
+          "slug",
+          "title",
+          "year",
+          "runtime_min",
+          "genres",
+          "directors",
+          "url",
+          "first_night",
+          "opening_venues"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "horizon_days": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "data_as_of",
+    "attribution",
+    "accuracy_url",
+    "horizon_days",
+    "film_count",
+    "films"
+  ],
+  "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 declare readOnlyHint=true and destructiveHint=false. The description goes beyond that by disclosing that every emitted showtime includes confidence, source tier, reporting sources and verified_at, and that showtimes_complete marks partial arrays — useful behavioral context for interpreting results.

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

Conciseness2/5

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

The opening is front-loaded and efficient, but the last two sentences contain a confusing 'In whats_playing' reference that appears copy-pasted from a different tool and repeats response-format details already in the schema. Those sentences do not earn their place and harm clarity.

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 the output schema exists, the description does not need to enumerate return fields; it supplies the core selection rule, sorting, configurable horizon, and data-provenance behavior. The whats_playing mis-reference is a notable flaw, but the tool remains callable based on the provided info.

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 schema already documents region, horizon_days, and response_format thoroughly. The description adds only the high-level 'Configurable horizon' and not much beyond what the schema provides, so the baseline 3 applies.

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 names a precise resource: films whose first screening on the board is more than 48 hours out, sorted by first night. This clearly separates it from scenef_whats_playing and scenef_search_showtimes, and the 'on-sale radar' phrasing conveys the intended booking use case.

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?

The 'worth booking early' phrasing implies when to use it, and 'Configurable horizon' hints at tuning, but there is no explicit when-to-use/when-not-to-use guidance or named alternatives. The agent must infer the tool's niche from the title and wording.

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?