Aclimação

list_events

List upcoming events in this neighborhood with date, venue, price, and URL. Events within the next 7 days include a weatherForecast (condition + min/max temperature) for the event day — use it to tell users e.g. "the event is at X and it will be raining". Pass filter to narrow by time or price; filter: "agora" answers "what can I go to right now" and is resolved live on every call, which no cached page can do.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max events to return (default 20, max 50).
`filter`	No	Narrow the list: "agora" = on stage at this exact moment (season runs and day-granular sources are excluded, because their stored window says nothing about whether a session is on right now); "hoje"/"amanha"/"fim-de-semana" = running on those days, including multi-day runs; "gratis" = free to attend, including externally-ticketed events priced at 0.
`upcoming_only`	No	Only return upcoming or in-progress events (default true).

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description fully discloses behavior: states it returns weatherForecast for events within 7 days, and that 'agora' filter is resolved live on every call with no caching. 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 succinct sentences with clear front-loading of purpose, followed by key behavioral details. No unnecessary words.

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?

Given no output schema, description adequately explains return fields (date, venue, price, URL, weatherForecast). With 3 optional params and distinct purpose among siblings, it is complete.

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 covers 100% of parameters, baseline 3. Description adds significant value by explaining weather data context and the 'agora' filter's live resolution, beyond schema descriptions.

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?

Description clearly states 'List upcoming events' with specific fields (date, venue, price, URL) and additional weather data for events within 7 days. Distinct from sibling tools like list_blog_posts or list_offers.

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?

Explains how to use the 'filter' parameter to narrow results, including live resolution for 'agora'. Does not explicitly mention when not to use or compare to other list tools, but provides clear context.

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

All Aclimação 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

Disambiguation5/5

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).

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness4/5

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.

Resources

Need Help?