SceneF — California, Florida and Hawaii Movie Showtimes

Discount grid

scenef_discounts

Read-only

Every structured discount across one board's theaters — venue, label, detail, and day-bound days — with the ones that apply today flagged.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.
`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
`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.

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

A4.1/5.0

Behavior4/5

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

Annotations (readOnlyHint=true, destructiveHint=false) already convey safety. The description adds behavioral context by mentioning that today's applicable discounts are flagged, which is useful. It doesn't specify other behaviors like sorting or pagination, but given annotations, this is sufficient.

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?

The description is a single, concise sentence that front-loads the core function and includes key attributes. It is efficient with no wasted words, making it easy to scan.

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 and the tool has only 2 optional parameters, the description covers the essential context. It doesn't explain edge cases like empty boards, but the output schema likely handles that. Overall, enough for an agent to call 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 description coverage is 100%, so parameters are fully documented. The description doesn't add much beyond the schema, but since the schema is complete and detailed (including error behavior for region, and response format details), the baseline of 3 is elevated to 4 because the schema itself is well-written and covers semantics.

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 clearly states the tool's purpose: listing structured discounts across a board's theaters with specific attributes (venue, label, detail, day-bound days) and flags applicable ones. It distinguishes from siblings by focusing on discounts, though it doesn't explicitly differentiate from related tools like scenef_whats_playing, but the purpose is clear.

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 implies usage context: querying discounts for a board's theaters. It doesn't explicitly state when not to use it or name alternatives, but the schema's response_format description mentions using scenef_search_showtimes for all times for one film/theatre, which gives partial guidance. This is clear but lacks explicit 'when not to use' statements.

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?