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?
Describes return content (cinemas, session times, format, language) and a requirement (movies_enabled). No annotations exist, so description carries burden. It accurately portrays a read-only query with no side effects, though could explicitly state idempotency.
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?
Two concise sentences: first defines purpose and output, second adds necessary precondition. No filler 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 2 parameters, no output schema, and no annotations, the description covers input, output, and required site setting. Sufficient for 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?
Adds meaning beyond schema: movie_slug source ('from list_movies'), date default ('today (BRT)'), and explains return format. Schema already covers date format and required field, but description enhances usability.
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?
States 'Get showtimes for a specific movie at cinemas in this neighborhood, for a given date' which is a specific verb+resource+scope. Clearly distinguishes from siblings like list_movies or get_event_tickets.
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?
Provides precondition 'Requires movies_enabled on this site.' Implicitly tells when to use: to retrieve showtimes for a movie on a specific date. No explicit when-not or alternative, but context is clear.
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 domain (e.g., bookings, events, places, restaurants, movies, forms) with clear boundaries. Even similar actions like create_booking and request_reservation are differentiated by service type (appointment vs restaurant table) and payment flow.
All 28 tools follow the consistent verb_noun snake_case pattern (e.g., create_booking, list_events, search_places). Verbs are appropriate and predictable, with no mixing of conventions.
28 tools is slightly above the typical range, but each tool serves a distinct purpose within the comprehensive neighborhood directory domain. The count is justified by the breadth of features (booking, events, restaurants, movies, etc.).
The tool surface covers most user needs: searching, viewing details, booking, reservations, events, forms, and more. Minor gaps exist, such as no cancellation tools for bookings/reservations, but the core workflows are well-supported.