Olé Futebol

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

Behavior4/5

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

Without annotations, the description discloses key behavior: weather data for events within 7 days and live resolution for 'agora' filter. Missing details on authentication, rate limits, or side effects, but adequate given simplicity.

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?

Three sentences that efficiently convey purpose, special feature, and parameter usage. No wasted words, front-loaded with main objective.

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?

For a tool with 3 optional params and no output schema, the description sufficiently explains return fields (date, venue, price, URL, weather) and filter semantics. Complete for its complexity.

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 has 100% coverage, but description adds context for filter enum values, especially 'agora' meaning live resolution. Adds value 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?

The description clearly states it lists upcoming events with specific fields (date, venue, price, URL) and a weather forecast for events within 7 days. This distinguishes it from sibling tools which focus on bookings, restaurants, etc.

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 concrete usage guidance via the `filter` parameter, especially for 'agora' resolving live. However, it does not explicitly state when not to use this tool or mention alternatives.

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

All Olé Futebol 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/5.0

Disambiguation5/5

Each tool targets a distinct resource or action (booking, checkout, availability, events, reviews, etc.). Even similar-looking tools like create_booking, request_reservation, and rsvp_event are clearly differentiated by their descriptions and target systems.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_booking_services). No mixing of conventions or unclear verbs.

Tool Count4/5

28 tools is on the higher end, but the server covers a wide domain (places, events, movies, booking, forms, loyalty, etc.). Each tool serves a clear purpose, so the count is justifiable, though minor trimming could be considered.

Completeness4/5

The tool set covers most workflows for a neighborhood directory: search, details, booking, events, reviews, etc. Some CRUD operations are missing (no update/delete for bookings), but these are consumer-facing actions where that is acceptable. The domain is well-covered.

Resources

Need Help?