Jardins

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

Behavior3/5

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

No annotations present; description covers behavioral aspects like weatherForecast inclusion and live resolution of 'agora' filter. Doesn't mention side effects or rate limits, but as a listing tool, read-only behavior is implied.

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?

Two clear sentences with key information front-loaded. Second sentence is slightly long but valuable. No redundancy or filler.

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?

No output schema, but description lists return fields (date, venue, price, URL, weatherForecast) adequately. For a list tool, it covers what users need to know about the output.

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 3. Description adds significant meaning: explains filter enum values in detail (e.g., 'agora' excludes season runs, 'gratis' includes externally-ticketed events at price 0), and notes limit default/max beyond schema.

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 it lists upcoming events with specific fields (date, venue, price, URL) and distinctive weatherForecast feature. Differentiates from siblings by mentioning filter 'agora' for live events, which is unique among list tools.

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 filter values like 'agora' and explains live resolution. Lacks explicit when-not-to-use or direct sibling comparison, but gives context for typical use cases.

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

All Jardins 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.2/5.0

Disambiguation5/5

Each tool targets a distinct action and resource, such as booking, checking availability, listing events, or searching dishes. No two tools appear to overlap in purpose, and descriptions clearly differentiate them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_events, search_places). The prefixes (create, get, list, search, request, reserve, rsvp, submit) are uniformly applied, and there is no mixing of cases or styles.

Tool Count4/5

With 28 tools, the server covers a broad feature set for a neighborhood directory, including bookings, store, events, loyalty, menus, movies, and more. While slightly high, each tool serves a distinct purpose and is justifiable.

Completeness5/5

The tool surface appears complete for the domain: search, details, booking flows, store purchases, events, loyalty, reviews, blog, offers, profiles, forms, and FAQ are all covered. There are no obvious dead ends, and operations for CRUD or lifecycle are present where needed.

Resources

Need Help?