SceneF — San Francisco Movie Showtimes

Right now

scenef_now

Read-only

The cheap is-anything-on call: how many screenings tonight, the next 5 curtains city-wide with venue/time/film, and dataset freshness per source. In "detailed" mode every showtime also carries its confidence level, source tier, reporting sources, and verified_at timestamp.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`response_format`	No	Output size: "concise" (default) for tight text lines, "detailed" to add ids, per-showtime ticket urls, and extra metadata.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`sources`	Yes
`night_of`	Yes
`data_as_of`	Yes
`is_tonight`	Yes
`attribution`	Yes
`accuracy_url`	Yes
`next_curtains`	Yes
`still_to_come`	Yes
`screenings_tonight`	Yes

TDQS

A4.5/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, so the safety profile is covered. The description adds valuable behavioral detail about output: it returns counts, freshness, and in detailed mode extra per-showtime metadata. It also implies lightweightness ('cheap'). No contradictions.

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?

Two efficient sentences. The first packs the core purpose and outputs, the second clarifies the mode-specific addition. Zero fluff, front-loaded with the 'cheap is-anything-on' hook and immediately informative.

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?

For a single-optional-parameter, read-only tool with an output schema present, the description fully covers what an agent needs to decide and call it correctly. It explains the count, the five shows with details, freshness, and the detailed mode extras. Nothing essential is missing.

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% and the parameter is well-documented. The description adds meaning beyond the schema by explicitly listing what the 'detailed' mode includes (confidence level, source tier, reporting sources, verified_at timestamp), which enriches the semantic understanding beyond the generic 'extra metadata' in the 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 states a specific verb ('call') and resource ('is-anything-on' for tonight), and lists concrete outputs: count, next 5 curtains city-wide with venue/time/film, and dataset freshness. It clearly distinguishes itself from siblings like scenef_coming_soon (future) and scenef_whats_playing (what's playing) by focusing on the immediate 'tonight' and the lightweight 'cheap' nature.

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 clear context by calling it 'the cheap is-anything-on call' and scoping to 'tonight' and 'next 5 curtains city-wide'. It implies when to use it (quick check for immediate availability) but does not explicitly state when-not to use it or name alternatives, which would push to a 5.

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

All SceneF — San Francisco Movie Showtimes tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

Most tools have clearly distinct query shapes: film lookup, theater card, discount list, coming-soon radar, and recommendation planner are easy to separate. Some overlap exists because several tools expose showtimes from different angles (e.g. scenef_whats_playing vs. scenef_now, and scenef_film_details vs. scenef_search_showtimes), but the descriptions provide enough grounding that an agent can usually select correctly.

Naming Consistency3/5

Every tool is prefixed with scenef_ and uses snake_case, which gives a consistent visual identity. Nevertheless, the pattern after the prefix is mixed: some names are nouns (scenef_discounts, scenef_accuracy), some are time references (scenef_now, scenef_coming_soon), and some are verb-first (scenef_search_showtimes, scenef_plan_movie_night). It is readable but not a single predictable verb_noun convention.

Tool Count5/5

Nine tools is right in the ideal range and each tool earns its place in the SF showtimes domain. The set covers discovery, detail lookups, discounts, recommendations, and data-accuracy verification without feeling padded or bloated.

Completeness4/5

The domain is covered broadly: film discovery, film details, theater details, per-film showtimes, coming soon, discounts, nightly overview, personalized planning, and accuracy metrics. The main gap is that there is no simple cross-film showtimes-for-a-specific-date listing, but agents can usually work around this with scenef_whats_playing and scenef_search_showtimes.

Resources

Need Help?