Skip to main content
Glama
bLd75

rundata · La Réunion 974 en direct

by bLd75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Événements à La Réunion : concerts, spectacles, fêtes, festivals, marchés

evenements
Read-onlyIdempotent

Find upcoming events in Réunion Island by town, type, or date, including concerts, markets, and festivals, with venue, price, and ticketing details.

Instructions

Événements à venir à La Réunion (974) : concerts, théâtre, danse, humour, cirque, soirées, fêtes, festivals, marchés, cinéma en plein air, animations municipales. D'après les programmes des salles (TÉAT Champ Fleuri et Plein Air, Cité des Arts et Palaxa, CDNOI, Kabardock, Le Séchoir, Léspas, Bisik, Théâtre Luc Donat), les agendas des mairies (Saint-Paul, Le Port, Les Trois-Bassins, Le Tampon, Saint-Louis, Saint-André, L'Étang-Salé, Entre-Deux, La Possession, Petite-Île, Bras-Panon, Saint-Benoît), de la CINOR et de l'office de tourisme du Nord (OpenAgenda) et reunion.fr. Chaque événement : titre, date et heures (heure de La Réunion), salle, commune, genre, prix et lien de billetterie quand ils sont donnés, statut (ANNULÉ, REPORTÉ, complet), y compris quand c'est un média de l'île qui l'annonce avant l'organisateur (statut_d_apres). Pour : « que faire ce week-end à Saint-Paul ? », « concert ce soir ? », « spectacle à Saint-Denis samedi ? », « marché forain demain ? », « c'est quand la fête de l'ail ? ». / Upcoming events in Réunion Island (concerts, shows, theatre, festivals, markets) from venues, town halls, OpenAgenda and the tourist board.

Input Schema

NameRequiredDescriptionDefault
lieuNoUne commune ou un lieu (« Saint-Paul », « Saint-Gilles ») : les événements de sa commune. Vide = toute l'île. / A town or place; empty = whole island.
quoiNoLe genre (« concert », « spectacle », « théâtre », « danse », « humour », « soirée », « festival », « marché », « cinéma », « enfants », « sport », « exposition ») ou des mots du titre ou de la salle (« ail », « dragon boat », « Kabardock ») ; vide = tout. / Kind, or words of the title or venue; empty = all.
quandNo« aujourd_hui », « ce_soir », « demain », « ce_week_end », « cette_semaine », « a_venir » (30 jours), un jour (« samedi ») ou une date (« 2026-10-31 ») ; vide = les 14 jours qui viennent. / When; empty = next 14 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.128.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, openWorldHint and idempotentHint, but the description adds meaningful behavioral context: events can be ANNULÉ, REPORTÉ or complet, and status may come from media reports before the organizer (statut_d_apres). It also lists source coverage, which helps an agent judge reliability. It does not discuss pagination, limits, or result ordering.

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

Conciseness3/5

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

The opening is well front-loaded, naming the resource, scope and categories. However, the description then becomes dense with long enumerations of venues, town halls and organizations, which adds bulk and slows scanning without materially changing how an agent should call the tool.

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 search tool with no output schema, the description is highly complete: it identifies the covered domains, sources, per-event fields, statuses, time zone, and common query shapes. An agent has enough information to decide to call it and to interpret the likely results.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already explains lieu, quoi and quand with examples and defaults. The description mentions the same categories and sources but does not add syntax, matching behavior, or edge-case semantics beyond what the schema provides. The baseline of 3 is appropriate.

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 states a specific resource and scope: upcoming events in Réunion (974), with concrete categories and named data sources. It is clearly an event-finding tool rather than news, weather, or a generic calendar, and the example queries make the intended use immediately recognizable.

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 gives strong usage cues through example queries such as « que faire ce week-end à Saint-Paul ? », « concert ce soir ? » and « marché forain demain ? ». It does not explicitly say when not to use it or name sibling alternatives such as actualites or calendrier, so it falls short of full when/when-not guidance.

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

Deploy Server

Other Tools