Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_search_sport_facilities

Search sport facilities in La Réunion including stadiums, gyms, swimming pools, tennis courts, and more. Returns equipment details, address, commune, and accessibility info from the national registry.

Instructions

Search the national sport-equipment registry (Recensement des Équipements Sportifs, RES) restricted to La Réunion. Covers all sport infrastructure: stadiums, gyms, swimming pools, tennis courts, boules courts, athletic tracks, climbing walls, skate parks, dojos, etc. Each row is one equipment within an installation. Returns installation and equipment names, type, family, address, postal code, commune, reduced-mobility accessibility, parking spaces. Source: Ministère des Sports via data.regionreunion.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoSport-equipment type prefix match. Examples: "Court de tennis", "Terrain de football", "Salle multisports", "Piste d'athlétisme", "Mur d'escalade"
familyNoEquipment family prefix match. Examples: "Petits terrains en accès libre", "Terrains de grands jeux", "Salles spécialisées", "Bassins de natation"
communeNoCommune name prefix match
limitNoMax facilities to return (1-500, default 50)

Implementation Reference

  • The tool handler for 'reunion_search_sport_facilities'. Calls the ReunionClient.getRecords method on the 'equipements-sportifs' dataset with optional filters (type, family, commune) and returns a JSON result with installation name, equipment name, type, family, address, postal code, commune, accessibility, and parking spaces.
    server.tool(
      'reunion_search_sport_facilities',
      'Search the national sport-equipment registry (Recensement des Équipements Sportifs, RES) restricted to La Réunion. Covers all sport infrastructure: stadiums, gyms, swimming pools, tennis courts, boules courts, athletic tracks, climbing walls, skate parks, dojos, etc. Each row is one equipment within an installation. Returns installation and equipment names, type, family, address, postal code, commune, reduced-mobility accessibility, parking spaces. Source: Ministère des Sports via data.regionreunion.com.',
      {
        type: z.string().optional().describe('Sport-equipment type prefix match. Examples: "Court de tennis", "Terrain de football", "Salle multisports", "Piste d\'athlétisme", "Mur d\'escalade"'),
        family: z.string().optional().describe('Equipment family prefix match. Examples: "Petits terrains en accès libre", "Terrains de grands jeux", "Salles spécialisées", "Bassins de natation"'),
        commune: z.string().optional().describe('Commune name prefix match'),
        limit: z.number().int().min(1).max(500).default(50).describe('Max facilities to return (1-500, default 50)'),
      },
      async ({ type, family, commune, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_SPORT, {
            where: buildWhere([
              type ? `type_d_equipement_sportif LIKE ${quote(`${type}%`)}` : undefined,
              family ? `famille_d_equipement_sportif LIKE ${quote(`${family}%`)}` : undefined,
              commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
            ]),
            limit,
          });
    
          return jsonResult({
            total_facilities: data.total_count,
            facilities: data.results.map((row) => ({
              installation_name: pickString(row, ['nom_de_l_installation_sportive']),
              equipment_name: pickString(row, ['nom_de_l_equipement_sportif']),
              type: pickString(row, ['type_d_equipement_sportif']),
              family: pickString(row, ['famille_d_equipement_sportif']),
              address: pickString(row, ['numero_type_et_nom_de_la_voie']),
              postal_code: pickString(row, ['code_postal']),
              commune: pickString(row, ['commune']),
              accessible: pickString(row, ['accessibilite_de_l_installation_en_faveur_des_personnes_en_situation_de_handicap']),
              parking_spaces: pickNumber(row, ['nombre_de_places_de_parking_reservees_a_l_installation']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search sport facilities');
        }
      }
    );
  • Zod schema for the tool's input parameters: type (string, optional), family (string, optional), commune (string, optional), limit (integer 1-500, default 50).
    {
      type: z.string().optional().describe('Sport-equipment type prefix match. Examples: "Court de tennis", "Terrain de football", "Salle multisports", "Piste d\'athlétisme", "Mur d\'escalade"'),
      family: z.string().optional().describe('Equipment family prefix match. Examples: "Petits terrains en accès libre", "Terrains de grands jeux", "Salles spécialisées", "Bassins de natation"'),
      commune: z.string().optional().describe('Commune name prefix match'),
      limit: z.number().int().min(1).max(500).default(50).describe('Max facilities to return (1-500, default 50)'),
    },
  • The tool is registered via server.tool() with name 'reunion_search_sport_facilities' inside the registerFacilityTools function in src/modules/facilities.ts.
      server.tool(
        'reunion_search_sport_facilities',
        'Search the national sport-equipment registry (Recensement des Équipements Sportifs, RES) restricted to La Réunion. Covers all sport infrastructure: stadiums, gyms, swimming pools, tennis courts, boules courts, athletic tracks, climbing walls, skate parks, dojos, etc. Each row is one equipment within an installation. Returns installation and equipment names, type, family, address, postal code, commune, reduced-mobility accessibility, parking spaces. Source: Ministère des Sports via data.regionreunion.com.',
        {
          type: z.string().optional().describe('Sport-equipment type prefix match. Examples: "Court de tennis", "Terrain de football", "Salle multisports", "Piste d\'athlétisme", "Mur d\'escalade"'),
          family: z.string().optional().describe('Equipment family prefix match. Examples: "Petits terrains en accès libre", "Terrains de grands jeux", "Salles spécialisées", "Bassins de natation"'),
          commune: z.string().optional().describe('Commune name prefix match'),
          limit: z.number().int().min(1).max(500).default(50).describe('Max facilities to return (1-500, default 50)'),
        },
        async ({ type, family, commune, limit }) => {
          try {
            const data = await client.getRecords<RecordObject>(DATASET_SPORT, {
              where: buildWhere([
                type ? `type_d_equipement_sportif LIKE ${quote(`${type}%`)}` : undefined,
                family ? `famille_d_equipement_sportif LIKE ${quote(`${family}%`)}` : undefined,
                commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
              ]),
              limit,
            });
    
            return jsonResult({
              total_facilities: data.total_count,
              facilities: data.results.map((row) => ({
                installation_name: pickString(row, ['nom_de_l_installation_sportive']),
                equipment_name: pickString(row, ['nom_de_l_equipement_sportif']),
                type: pickString(row, ['type_d_equipement_sportif']),
                family: pickString(row, ['famille_d_equipement_sportif']),
                address: pickString(row, ['numero_type_et_nom_de_la_voie']),
                postal_code: pickString(row, ['code_postal']),
                commune: pickString(row, ['commune']),
                accessible: pickString(row, ['accessibilite_de_l_installation_en_faveur_des_personnes_en_situation_de_handicap']),
                parking_spaces: pickNumber(row, ['nombre_de_places_de_parking_reservees_a_l_installation']),
              })),
            });
          } catch (error) {
            return errorResult(error instanceof Error ? error.message : 'Failed to search sport facilities');
          }
        }
      );
    }
  • registerFacilityTools is called from src/modules/index.ts -> registerAllTools, which is invoked from src/index.ts (line 22).
    registerFacilityTools(server);
  • buildWhere helper combines filter conditions with AND; quote helper for ODSQL string escaping.
    export function buildWhere(
      conditions: Array<string | undefined | null | false>
    ): string | undefined {
      const valid = conditions.filter((condition): condition is string => Boolean(condition));
      return valid.length > 0 ? valid.join(' AND ') : undefined;
    }
Behavior2/5

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

No annotations provided. Description does not disclose whether the tool is read-only, idempotent, or has any side effects. As a search tool, it is likely safe, but not explicitly stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences only, front-loaded with purpose and scope, then details. No extraneous information.

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?

No output schema, but description explains return fields comprehensively. Mentions source. Lacks pagination details, but limit parameter covers that. Adequate for a search tool with 4 optional params.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters. Description adds value by providing concrete examples for type and family (e.g., 'Court de tennis', 'Petits terrains en accès libre') and explains limit's default and range. Enhances understanding beyond 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?

Clearly states it searches the national sport-equipment registry (RES) restricted to La Réunion. Lists specific examples (stadiums, gyms, etc.) and return fields. Distinct from sibling tools like reunion_list_swimming_pools which is more specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for general sport infrastructure search in Réunion but does not explicitly state when to use vs alternatives like reunion_list_swimming_pools. No when-not guidance or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Hug0x0/mcp-reunion'

If you have feedback or need assistance with the MCP directory API, please join our Discord server