Skip to main content
Glama
Sign In

rundata.re · La Réunion en direct

by re.rundata
OverviewDiscussionsAdmin

Vacances, jours fériés, soleil et Lune à La Réunion

calendrier
Read-only

Calendrier de La Réunion (974) : vacances scolaires de l'académie de La Réunion (calendrier austral, différent de la métropole), jours fériés (dont le 20 décembre, Fèt Kaf), date du jour, heures de lever et de coucher du soleil au lieu demandé, et la Lune : phase, part éclairée, lever et coucher, prochaines phases (calculés). Pour : « c'est quand les vacances ? », « le 20 décembre est férié ? », « la Lune se lève à quelle heure ce soir ? ».

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calendrier"
  }
}

Input Schema

NameRequiredDescriptionDefault
lieuNoLieu à La Réunion : commune, plage, quartier, cirque, sommet, ou coordonnées « -21.05, 55.22 ». Vide = toute l'île.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / lieu / description
      Previous value: -"Lieu à La Réunion, en texte libre : commune (« Saint-Paul »), plage (« plage de l'Hermitage », « Boucan Canot »), quartier, cirque (« Cilaos », « Mafate »), sommet (« Maïdo », « volcan »), ou coordonnées « -21.05, 55.22 ». Vide = tour de l'île. / Place in Réunion, free text or 'lat, lon'; empty = whole island."New value: +"Lieu à La Réunion : commune, plage, quartier, cirque, sommet, ou coordonnées « -21.05, 55.22 ». Vide = toute l'île."
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful domain context: values are computed ("calculés"), the calendar is austral and island-specific (974), and sun/moon data depends on the requested location. It does not say whether all sections are always returned or how fresh/cached the data is.

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?

Front-loaded with the scope ("Calendrier de La Réunion (974)") followed by a compact enumeration of covered data and then example queries. Dense but every clause carries information; no 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?

The description enumerates the data domains the tool covers, which substitutes for the missing output schema. The only residual gap is whether a call returns all domains at once or must be scoped — minor for a read-only, single-optional-parameter tool.

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 single `lieu` parameter is already fully documented, including the empty-string default meaning the whole island. The description only echoes this with "au lieu demandé" and adds no format or precision guidance beyond the 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?

States a specific resource and enumerates its concrete contents: school holidays for the Réunion academy, public holidays including 20 December (Fèt Kaf), today's date, sunrise/sunset at a given location, and moon phase/rise/set. It also explicitly distinguishes the austral school calendar from the metropolitan one, so an agent can separate it from siblings like maree or meteo_actuelle.

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 :" clause supplies three concrete example questions that map cleanly onto when to call this tool (holiday dates, whether 20 December is a holiday, moon rise time tonight). It gives clear usage context but names no alternative sibling tools and states no when-not-to-use condition.

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

All rundata.re · La Réunion en direct toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources