Skip to main content
Glama
bLd75

rundata · La Réunion 974 en direct

by bLd75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Sport à La Réunion : matchs, résultats, annulations, Grand Raid

sport
Read-onlyIdempotent

Find upcoming matches and official results for handball, volleyball, sailing, golf, rallying and Grand Raid in Réunion, including locations, cancellations, standings and club news.

Instructions

Sport à La Réunion (974) : matchs à venir et derniers résultats officiels des championnats régionaux de handball (D1) et de volley (R1 et R2, hommes et femmes, toutes les poules), avec les clubs en toutes lettres (VBSP = Volley-Ball de Saint-Pierre) et la commune où l'on joue, les matchs annulés ou reportés (avis de la Ligue de volley, actualité locale), classements, régates de voile, compétitions de golf, rallyes et sport automobile (calendrier de la Ligue), Grand Raid (courses, partants, abandons, podiums), les programmes sportifs publiés par les communes (le lien du document de la mairie, sans son contenu), et l'actualité sportive de Réunion La 1ère (titres et liens, dont le football et le basket). Pour : « match de volley dimanche dans le sud ? », « match de hand ce week-end à Saint-Pierre ? », « le TGV joue quand ? », « foot ou basket ce week-end ? », « résultats du volley à Saint-Leu ? », « classement du handball ? », « prochaine régate ? », « prochain rallye ? », « qui a gagné le Grand Raid ? ». / Sport in Réunion Island: fixtures, results, cancellations, standings, Grand Raid.

Input Schema

NameRequiredDescriptionDefault
lieuNoUne commune (« Saint-Paul »), une partie de l'île (« le sud », « l'ouest », « le nord », « l'est ») ou un club (« VBSP », « Tampon Gecko Volley ») : ce qui s'y joue et ses clubs à l'extérieur. Vide = toute l'île. / A town, part of the island or club; empty = whole island.
quandNo« aujourd_hui », « demain », « samedi » ou « dimanche » (le prochain), « ce_week_end », « a_venir » (14 jours) ou « resultats » ; vide = les deux. / Today, tomorrow, next Saturday or Sunday, this weekend, upcoming or results; empty = both.
sportNoLe sport ; vide = tous. « football » et « basket » renvoient l'actualité seulement (pas de résultats officiels lus). / The sport; empty = all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.128.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld behavior, and the description adds useful source and limitation context: official league results, local cancellation notices, commune documents exposed as links without their content, and football/basket as news only. It does not explain freshness guarantees or return formatting, but it goes well beyond the annotations.

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 scope is front-loaded, but the main sentence is a long run-on enumeration followed by many example queries and an English summary. The length is somewhat justified by the broad domain, yet it is not concise or cleanly structured.

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?

For a broad, read-only discovery tool with three optional parameters and no output schema, the description covers supported sports, data types, sources, and important limitations such as link-only commune programs. It lacks explicit sibling routing and return-format details, but is otherwise sufficient to call correctly.

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%, and the schema already explains lieu, quand, and sport, including enum values and empty-parameter behavior. The description reinforces these with examples but adds little semantic detail beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific domain and resources: upcoming matches, official results, cancellations, standings, Grand Raid, and sport-specific news for Réunion. It is clearly distinguishable from generic news or events tools by its sports scope, though it does not explicitly name sibling tools such as actualites or evenements for routing.

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 'Pour :' examples give concrete triggers such as volleyball matches on Sunday, handball results, standings, regattas, rallies, and Grand Raid winners. It does not state when not to use this tool or explicitly redirect general sports news to siblings like actualites.

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