Skip to main content
Glama

Tatuapé

by io.github.junoventures

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
NameRequiredDescriptionDefault
limitNoMax events to return (default 20, max 50).
filterNoNarrow 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_onlyNoOnly 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?

With no annotations provided, the description carries full burden. It discloses weather forecast inclusion, explains the live resolution of the 'agora' filter, and notes exclusions for season runs and day-granular sources. No contradictory information.

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?

The description is three sentences with no superfluous words. Every sentence adds value: purpose, weather forecast feature, and filter usage clarification. It is front-loaded with the main purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema, the description provides a good overview of return fields (date, venue, price, URL, weatherForecast for 7-day events). It could mention ordering or pagination but is sufficient for a listing tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds significant value: it explains each filter enum value in detail (e.g., 'hoje' includes multi-day runs), states defaults for limit and upcoming_only, and highlights that 'agora' is resolved live. This goes beyond the schema's 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?

The description clearly states 'List upcoming events in this neighborhood with date, venue, price, and URL' – a specific verb and resource. It distinguishes itself from sibling tools like list_offers or list_movies by detailing the fields returned and the inclusion of weather forecasts for events within 7 days.

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?

The description explains when to use the filter parameter, especially for 'agora' to find currently running events, and contrasts with cached pages. It provides use case examples but does not explicitly compare to siblings outside of the filter context.

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

All Tatuapé toolsInspect
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 has a clearly distinct purpose, even among similar actions like booking, reservation, and ticket purchase—their descriptions clarify the domain and flow. No two tools could reasonably be confused.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_blog_posts). There are no deviations or mixed conventions.

Tool Count3/5

At 28 tools, the surface is larger than ideal for a single server, but each tool covers a distinct feature of the neighborhood directory (bookings, events, store, etc.). It borders on heavy but is still manageable for an agent.

Completeness5/5

The tool set covers the full lifecycle of browsing and acting on a neighborhood directory: search, details, reviews, menus, events, booking, reservations, store, loyalty, and more. No obvious gaps exist for the intended use case.

Resources