rundata.re · La Réunion en direct

Électricité à La Réunion en ce moment

electricite

Read-only

Électricité à La Réunion (974) en direct, d'après EDF : production totale, part de chaque filière et part renouvelable, mises à jour toutes les 5 min ; « météo de l'électricité » d'EDF pour les jours qui viennent (heures de pointe, réseau contraint, recharge conseillée d'un véhicule électrique). Pour : « d'où vient l'électricité ? », « quand recharger ma voiture électrique ? ». Coupures de courant (électricité, pas l'eau : coupures_eau) : les avis d'EDF que relaient les mairies dont le site ne l'interdit pas (Sainte-Marie), jours, heures et secteurs, avec le lien de l'avis. Pour : « coupure de courant à Sainte-Marie ? », « coupure EDF prévue dans ma commune ? ».

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": "electricite"
  }
}

Input Schema

Name	Required	Description	Default
`lieu`	No	Lieu à 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.

Changed1 schema field changedOct 26, 2026

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."

Changed1 schema field changedOct 26, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```

Changed1 schema field changedOct 24, 2026

addedInput schema / properties / lieu

Added value: +{
+  "description": "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.",
+  "type": "string"
+}

AddedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish readOnly/openWorld/non-destructive, so the bar is lower, and the description still adds real behavioral context: 5-minute refresh cadence, EDF as data source, and an important coverage caveat that outage data exists only for communes whose sites permit relaying. It does not describe pagination or response shape, but the freshness and coverage disclosures are the substantive risks an agent would otherwise miss.

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?

The main purpose is front-loaded in the first clause (production mix, 5-min updates) before the outage block, and every sentence carries useful information, including the explicit coupures_eau disambiguation. It is dense — layered parentheses, guillemets, and repeated 'Pour :' blocks — but not padded; trimming further would lose the coverage caveat.

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?

There is no output schema, so the description must carry the return-value burden, and it does: it enumerates the production figures, per-filière shares, renewable share, upcoming peak/constrained-grid/recharge windows, and outage notices with days, hours, sectors and a link to the avis. Combined with the schema's single well-documented parameter, an agent has everything needed to call and interpret the result.

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 single optional 'lieu' parameter is fully documented in the schema (commune, beach, quartier, cirque, summit, or '-21.05, 55.22' coordinates; empty = whole island). The description adds no syntax or behavioral nuance about the parameter beyond what the schema already states, so the baseline 3 applies.

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 names concrete resources: live electricity production mix for La Réunion (total production, per-source share, renewable share, refreshed every 5 min), EDF's short-term 'météo de l'électricité', and EDF outage notices relayed by mairies. It explicitly distinguishes itself from the water-outage sibling ('électricité, pas l'eau : coupures_eau'), so an agent can separate it from coupures_eau without opening a schema.

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?

Usage is anchored in literal user phrasings ('d'où vient l'électricité ?', 'quand recharger ma voiture électrique ?', 'coupure EDF prévue dans ma commune ?'), and the coverage boundary is stated: only mairies whose site does not forbid it (Sainte-Marie). What is missing is routing to the relevant siblings — bornes_recharge for locating charging points, or the general forecast/actualités tools — so the alternative-selection guidance is implied rather than complete.

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 tools Inspect

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.