Skip to main content
Glama
Sign In

rundata.re · La Réunion en direct

by re.rundata
OverviewDiscussionsAdmin

Défibrillateurs à La Réunion

defibrillateurs
Read-only

Défibrillateurs (DAE) les plus proches d'un lieu de La Réunion (974), d'après la base nationale Géo'DAE : adresse, distance et temps à pied, emplacement exact, accessible à toute heure ou aux heures d'ouverture. Pour : « où est le défibrillateur le plus proche de la plage de l'Hermitage ? », « défibrillateur à Cilaos ? ». Dire d'abord d'appeler le 15 ou le 112 et de commencer le massage cardiaque.

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

Input Schema

NameRequiredDescriptionDefault
lieuNoLe lieu sur lequel on s'interroge, pas la position de l'utilisateur : commune, plage, quartier, cirque, sommet. 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 : commune, plage, quartier, cirque, sommet, ou coordonnées « -21.05, 55.22 ». Vide = toute l'île."New value: +"Le lieu sur lequel on s'interroge, pas la position de l'utilisateur : commune, plage, quartier, cirque, sommet. Vide = toute l'île."
  2. 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."
  3. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety of the call is covered. The description adds real context beyond that: the upstream data source (Géo'DAE), the returned fields (adresse, distance et temps à pied, emplacement exact), and the fact that accessibility varies (24h/24 vs heures d'ouverture). It does not discuss result limits or fallback when the place is unknown.

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 core capability is front-loaded in the first sentence, with the data source and returned fields attached to it, and the examples immediately after. The trailing first-aid instruction ('appeler le 15 ou le 112 et commencer le massage cardiaque') is on-topic for a life-safety tool but is a response instruction rather than a tool-selection aid, so it is slightly extraneous to the definition's job.

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, and the description compensates by enumerating what a result contains (address, distance and walking time, exact location, accessibility hours). For a single-optional-parameter lookup, that leaves nothing an agent needs in order to call it 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 coverage is 100% and the single 'lieu' parameter is already well documented in the schema, including the empty-value behaviour. The description reinforces the place-based framing ('les plus proches d'un lieu') but adds no syntax or format detail beyond the schema, 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?

Names the exact resource (Défibrillateurs / DAE), the scope (les plus proches d'un lieu de La Réunion, 974) and the source (base nationale Géo'DAE), so the agent knows precisely what it returns. No sibling tool in the list covers this domain, and the two example queries pin the intent further.

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 plus two quoted example questions make the trigger condition explicit (locating the nearest defibrillator at a named place). There are no alternative tools in this domain to exclude, so the absence of when-not guidance is low-cost, but it is still not spelled out.

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