Skip to main content
Glama

DOJO+

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

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

With no annotations, the description carries the full burden and does well by disclosing the weather forecast behavior for the next 7 days, the live resolution of 'agora', and the exclusion of season/day-granular sources for that filter. It does not state read-only or idempotency, but for a list operation that is less critical.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core purpose and outputs. The second sentence packs filter semantics and live behavior efficiently, though it is slightly dense with parentheticals. Still, every clause earns its place.

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?

Without an output schema, the description adequately lists return fields (date, venue, price, URL, weatherForecast) and covers edge cases like multi-day runs and free events. It does not mention pagination or error behavior, but for a simple list tool with three optional parameters, coverage is strong.

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%, so baseline is 3, but the description adds real meaning: it explains the 'agora' filter semantics, clarifies 'gratis' includes externally-ticketed zero-price events, and ties weatherForecast to the date field. This goes beyond the schema's simple enum labels.

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 a specific verb ('List'), resource ('events in this neighborhood'), and output fields ('date, venue, price, and URL'). It distinguishes from sibling listing tools like list_movies and list_blog_posts by scoping to neighborhood events and adding the weather forecast detail.

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?

Provides explicit guidance on using the 'filter' parameter, especially the 'agora' value for live results, and contrasts it with cached pages. However, it does not explicitly mention when to prefer this tool over sibling event-related tools like get_showtimes or get_event_tickets, so it lacks full alternative differentiation.

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

All DOJO+ 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 targets a distinct resource or action (e.g., create_booking vs create_checkout, reserve_event_tickets vs rsvp_event), and descriptions provide clear boundaries. Even closely related tools like list_booking_services and list_pricing_plans are differentiated by context.

Naming Consistency5/5

All 26 tools follow a consistent snake_case verb_noun pattern (get_, list_, create_, search_, etc.), with no mixed conventions or vague verbs. This makes the tool set predictable and easy to navigate.

Tool Count3/5

At 26 tools, the set is on the heavy side and exceeds the typical well-scoped range, but the diversity reflects a multi-featured directory covering bookings, events, store, reviews, forms, and more. Each tool appears to serve a distinct purpose, so the count is borderline rather than excessive.

Completeness4/5

The surface covers the core user workflows: search, view details, book services, reserve/RSVP events, request reservations, submit forms, and browse content. Minor gaps exist (e.g., no cancellation/update for bookings, no full blog post body), but these are workarounds and not critical for a consumer-facing directory.

Resources