Skip to main content
Glama

Centro

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.5/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that events within 7 days include a weather forecast and that 'agora' is resolved live on every call. While it does not explicitly mention safety or idempotency, as a read-only list operation, this is sufficient.

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 concise, front-loads the primary purpose, and includes all necessary information in two sentences without extraneous text. Every sentence adds value.

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 the tool's simplicity and absence of an output schema, the description fully covers return values (date, venue, price, URL, optional weather) and parameter usage. It provides enough context for an agent to invoke the tool correctly.

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 coverage is 100%, but the description adds significant meaning beyond the schema by explaining the 'filter' enum values in detail (e.g., 'agora' for currently running events, 'hoje'/'amanha' for multi-day events). This helps the agent select the correct filter.

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 the tool lists upcoming events with key fields (date, venue, price, URL). The verb 'List' and resource 'upcoming events' are specific, distinguishing it from sibling tools like 'get_event_tickets' or 'reserve_event_tickets'.

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 provides guidance on using the 'filter' parameter to narrow results and explains the 'agora' option as a live, real-time query. It does not explicitly state when not to use the tool or mention alternatives, but the context is clear.

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

All Centro 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.2/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose. Tools like create_booking and request_reservation target different services (appointments vs. restaurant tables), and reserve_event_tickets vs. rsvp_event differentiate paid holds from free RSVPs. No overlapping functionality that would confuse an agent.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_dishes) using lowercase with underscores. No mixing of conventions or irregular verbs.

Tool Count4/5

28 tools cover a broad domain of neighborhood directory services (bookings, events, movies, restaurant menus, forms, etc.). While the count is slightly high, each tool serves a specific function and is justified by the domain scope.

Completeness5/5

The tool set provides comprehensive coverage for a neighborhood directory: search, booking, reservations, event management, menus, reviews, forms, loyalty, and more. No obvious gaps; all core user needs are addressed.

Resources