Get showtimes for a specific movie at cinemas in this neighborhood, for a given date. Returns each cinema with session times, format (e.g. "Laser", "3D"), and language (Dublado/Legendado). Requires movies_enabled on this site.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Date in YYYY-MM-DD format. Defaults to today (BRT). | |
| movie_slug | Yes | Movie slug from list_movies (e.g. "o-corvo-1016084"). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the requirement of movies_enabled, but does not mention side effects, rate limits, or authentication needs. Since it is a read operation, the lack of destructive hint is fine, but more detail on caching or data freshness could help.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the action and result, and every sentence adds necessary context—no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple two-parameter input and no output schema, the description fully explains what the tool does, what it returns (cinema, times, format, language), and the prerequisite (movies_enabled). It is complete for an agent to select and invoke correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the description adds value by clarifying that movie_slug comes from list_movies with an example, and that date defaults to today in BRT format. This adds meaning beyond the schema's descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it retrieves showtimes for a specific movie at cinemas in the neighborhood for a given date, specifying the returned fields (cinema, session times, format, language). It distinguishes itself from siblings by focusing on movie showtimes, contrasting with unrelated tools like get_availability or list_events.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description mentions the prerequisite 'movies_enabled on this site' and implicitly guides the user to use list_movies to obtain the movie_slug. However, it does not explicitly state when not to use this tool or compare with alternatives, though no direct sibling overlaps.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource or action: appointments, products, events, places, menus, reviews, forms, etc. No two tools have overlapping purposes; even similar booking tools (create_booking, request_reservation, reserve_event_tickets, rsvp_event) are clearly differentiated by description and use case.
All tool names follow a consistent verb_noun pattern using lowercase with underscores (e.g., create_booking, list_events, search_places). Verbs are appropriate (create, get, list, search, submit, request, reserve, rsvp) and nouns clearly indicate the resource.
28 tools cover a broad domain (neighborhood directory with Wix integrations). While each tool has a clear purpose, the count exceeds the typical 3-15 range slightly, making the surface feel somewhat heavy but still manageable.
The tool surface provides comprehensive coverage for the domain: discovery (search places, list events, list guides), details (get place, get reviews), booking (appointments, restaurant, event tickets, RSVP), checkout, forms, FAQs, loyalty, pricing plans, and more. No obvious dead ends for common user journeys.
