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, the description fully describes the return values (cinema, times, format, language) and a key requirement (movies_enabled). It does not mention rate limits or auth, but the transparency is adequate for a read-only query.
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 sentences: first sentence states purpose and output, second sentence states a prerequisite. No fluff, every sentence adds value.
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?
For a simple tool with 2 parameters and no output schema, the description covers purpose, output details, and a prerequisite. It is complete for an agent to understand when and how to use it.
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%, so baseline is 3. The description adds value by explaining the date default (today BRT) and providing an example for movie_slug. It also clarifies what the output contains beyond the schema.
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 verb 'Get showtimes' and the resource 'for a specific movie at cinemas in this neighborhood, for a given date'. It distinguishes itself from siblings by focusing specifically on showtimes and not other functions like list_movies or get_availability.
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 includes a prerequisite ('Requires movies_enabled on this site') and implies you need a movie_slug from list_movies. It does not explicitly state when not to use it, but the context is clear enough for appropriate use.
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 (booking, events, places, food, movies, etc.) with clear boundaries. Even similar actions like reservations are clearly differentiated by context (booking appointment vs. table vs. event tickets vs. RSVP).
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_events, search_places). No mixing of conventions or vague verbs.
28 tools is on the higher end but justifiable for a comprehensive neighborhood directory covering bookings, events, store, reviews, FAQs, guides, offers, movies, and more. Each tool serves a specific purpose without redundancy.
The tool surface covers the main user workflows (searching places, booking services, events, food ordering, loyalty, reviews). Minor gaps like lack of user account management or direct payment handling are acceptable for a directory MCP.