Skip to main content
Glama
Sign In

rundata.re · La Réunion en direct

by re.rundata
OverviewDiscussionsAdmin

Bornes de recharge à La Réunion

bornes_recharge
Read-only

Bornes de recharge publiques pour voiture électrique à La Réunion et l'état en direct de chaque point d'après son opérateur : libre, occupé ou hors service, avec sa puissance et ses prises. Pour : « borne de recharge libre près de Saint-Gilles ? », « où recharger rapidement à Saint-Pierre ? », « bornes au Tampon ? ».

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

Input Schema

NameRequiredDescriptionDefault
lieuNoUn lieu ou une commune (« Saint-Gilles-les-Bains », « Le Tampon », « aéroport Roland-Garros »). Vide = toute l'île.
rapideNoSeulement la recharge rapide (50 kW ou plus).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / lieu / description
      Previous value: -"Un lieu ou une commune (« Saint-Gilles-les-Bains », « Le Tampon », « aéroport Roland-Garros »). Vide = toute l'île. / A place or town; empty = whole island."New value: +"Un lieu ou une commune (« Saint-Gilles-les-Bains », « Le Tampon », « aéroport Roland-Garros »). Vide = toute l'île."
    • changedInput schema / properties / rapide / description
      Previous value: -"Seulement la recharge rapide (50 kW ou plus). / Fast charging only (50 kW or more)."New value: +"Seulement la recharge rapide (50 kW ou plus)."
  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, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the status comes from each point's operator ('d'après son opérateur') and is live ('état en direct'), implying freshness and third-party provenance. It does not explain staleness, coverage of operators/networks, or how unlisted/private chargers are handled, which would matter for trusting the live state.

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 resource and the returned data, then a short 'Pour :' block of representative queries. Slightly long on examples, but each one demonstrates a different parameter combination (location, speed, town) and earns its place.

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 two-optional-parameter read tool with no output schema, the description covers what matters: what is searched, where, and what comes back (status, power, connectors). Missing only peripheral details such as operator coverage or data refresh cadence; annotations already handle the safety profile.

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 coverage is 100%, so both parameters (lieu, rapide) are already fully documented, including that empty lieu means the whole island and that rapide means 50 kW or more. The description only echoes these concepts through its examples ('près de Saint-Gilles', 'recharger rapidement'), adding marginal meaning; baseline 3 applies when the schema does the heavy lifting.

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 (public EV charging stations in La Réunion) with the exact attributes returned: live status per point (libre/occupé/hors service), power, and connectors. The three example queries (« borne libre près de Saint-Gilles », « où recharger rapidement à Saint-Pierre », « bornes au Tampon ») make the scope unmistakable and keep it distinct from siblings like electricity, transports, or velos_libre_service.

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 example questions clearly signal the situations that should route here (finding a free charger, finding fast charging, listing chargers in a town). There is no explicit exclusion or pointer to an alternative sibling, but no sibling realistically overlaps with live charger status, so the routing guidance is effectively clear.

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