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?
With no annotations provided, the description discloses the behavioral constraint (movies_enabled requirement) and implies a read operation. It does not contradict anything, and the behavior is transparent for a simple retrieval tool.
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 concise (two sentences) and well-structured: first sentence defines purpose and output, second sentence adds a critical prerequisite. No unnecessary 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 low parameter count, no output schema, and no nested objects, the description sufficiently explains what the tool does and returns (cinema, times, format, language). The prerequisite adds necessary context for correct invocation.
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 description coverage is 100%, but the description adds value by noting that date defaults to today (BRT) and that movie_slug comes from list_movies. This helps the agent understand parameter origins and defaults.
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 the tool retrieves showtimes for a specific movie at local cinemas for a given date, specifying output details (cinema, times, format, language). It distinguishes itself from sibling tools like get_event_tickets or get_restaurant_menus, which are unrelated.
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 provides context by noting the prerequisite 'Requires movies_enabled on this site.' However, it does not explicitly mention when to use this tool over alternatives or exclusions, but the context is clear enough for a read-only lookup tool.
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 action and resource, such as booking, checking availability, listing events, or searching dishes. No two tools appear to overlap in purpose, and descriptions clearly differentiate them.
All tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_events, search_places). The prefixes (create, get, list, search, request, reserve, rsvp, submit) are uniformly applied, and there is no mixing of cases or styles.
With 28 tools, the server covers a broad feature set for a neighborhood directory, including bookings, store, events, loyalty, menus, movies, and more. While slightly high, each tool serves a distinct purpose and is justifiable.
The tool surface appears complete for the domain: search, details, booking flows, store purchases, events, loyalty, reviews, blog, offers, profiles, forms, and FAQ are all covered. There are no obvious dead ends, and operations for CRUD or lifecycle are present where needed.