Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_search_tourism_establishments

Search tourism establishments in La Réunion (hotels, restaurants, gîtes, activity providers, etc.) by type, commune, zone, or keyword. Returns commercial name, classification, address, payment methods, and tourist office.

Instructions

Search the SIT Soubik (Système d'Information Touristique) catalog for La Réunion: hotels, restaurants, gîtes, activity providers, leisure venues, tour operators, transport providers serving tourists. Returns commercial name, type, classification, commune, tourism zone (Nord/Sud/Est/Ouest/Cirques/Volcan), address, accepted payment methods, attached tourist office. For star-classified accommodations specifically, use reunion_search_classified_accommodations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoEstablishment type prefix match. Examples: "Hôtel", "Restaurant", "Gîte", "Camping", "Activité de loisirs", "Office de tourisme"
communeNoCommune name prefix match
zoneNoTourism zone prefix match. Examples: "Nord", "Sud", "Est", "Ouest", "Cirques", "Volcan"
queryNoFree-text search on commercial name and address
limitNoMax establishments to return (1-300, default 50)

Implementation Reference

  • The registerHospitalityTools function registers the 'reunion_search_tourism_establishments' tool with the MCP server.
    export function registerHospitalityTools(server: McpServer): void {
      server.tool(
        'reunion_search_tourism_establishments',
        'Search the SIT Soubik (Système d\'Information Touristique) catalog for La Réunion: hotels, restaurants, gîtes, activity providers, leisure venues, tour operators, transport providers serving tourists. Returns commercial name, type, classification, commune, tourism zone (Nord/Sud/Est/Ouest/Cirques/Volcan), address, accepted payment methods, attached tourist office. For star-classified accommodations specifically, use reunion_search_classified_accommodations.',
        {
          type: z.string().optional().describe('Establishment type prefix match. Examples: "Hôtel", "Restaurant", "Gîte", "Camping", "Activité de loisirs", "Office de tourisme"'),
          commune: z.string().optional().describe('Commune name prefix match'),
          zone: z.string().optional().describe('Tourism zone prefix match. Examples: "Nord", "Sud", "Est", "Ouest", "Cirques", "Volcan"'),
          query: z.string().optional().describe('Free-text search on commercial name and address'),
          limit: z.number().int().min(1).max(300).default(50).describe('Max establishments to return (1-300, default 50)'),
        },
        async ({ type, commune, zone, query, limit }) => {
          try {
            const data = await client.getRecords<RecordObject>(DATASET_ESTABLISHMENTS, {
              where: buildWhere([
                type ? `type LIKE ${quote(`${type}%`)}` : undefined,
                commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
                zone ? `zone_touristique LIKE ${quote(`${zone}%`)}` : undefined,
                query ? `search(${quote(query)})` : undefined,
              ]),
              limit,
            });
            return jsonResult({
              total_establishments: data.total_count,
              establishments: data.results.map((row) => ({
                name: pickString(row, ['nom_commercial']),
                type: pickString(row, ['type']),
                classification: pickString(row, ['classement']),
                commune: pickString(row, ['commune']),
                tourism_zone: pickString(row, ['zone_touristique']),
                address: pickString(row, ['adresse']),
                payment_methods: pickString(row, ['modes_de_paiement']),
                tourist_office: pickString(row, ['offices_de_tourisme']),
              })),
            });
          } catch (error) {
            return errorResult(error instanceof Error ? error.message : 'Failed to search tourism establishments');
          }
        }
      );
  • The async handler that queries OpenDataSoft dataset 'etablissements-touristiques-lareunion-wssoubik', applies filters, maps results to clean response fields.
    async ({ type, commune, zone, query, limit }) => {
      try {
        const data = await client.getRecords<RecordObject>(DATASET_ESTABLISHMENTS, {
          where: buildWhere([
            type ? `type LIKE ${quote(`${type}%`)}` : undefined,
            commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
            zone ? `zone_touristique LIKE ${quote(`${zone}%`)}` : undefined,
            query ? `search(${quote(query)})` : undefined,
          ]),
          limit,
        });
        return jsonResult({
          total_establishments: data.total_count,
          establishments: data.results.map((row) => ({
            name: pickString(row, ['nom_commercial']),
            type: pickString(row, ['type']),
            classification: pickString(row, ['classement']),
            commune: pickString(row, ['commune']),
            tourism_zone: pickString(row, ['zone_touristique']),
            address: pickString(row, ['adresse']),
            payment_methods: pickString(row, ['modes_de_paiement']),
            tourist_office: pickString(row, ['offices_de_tourisme']),
          })),
        });
      } catch (error) {
        return errorResult(error instanceof Error ? error.message : 'Failed to search tourism establishments');
      }
    }
  • Zod schema for input parameters: type, commune, zone, query (optional strings), limit (1-300, default 50).
    {
      type: z.string().optional().describe('Establishment type prefix match. Examples: "Hôtel", "Restaurant", "Gîte", "Camping", "Activité de loisirs", "Office de tourisme"'),
      commune: z.string().optional().describe('Commune name prefix match'),
      zone: z.string().optional().describe('Tourism zone prefix match. Examples: "Nord", "Sud", "Est", "Ouest", "Cirques", "Volcan"'),
      query: z.string().optional().describe('Free-text search on commercial name and address'),
      limit: z.number().int().min(1).max(300).default(50).describe('Max establishments to return (1-300, default 50)'),
    },
  • Dataset constant 'etablissements-touristiques-lareunion-wssoubik' used as the data source.
    const DATASET_ESTABLISHMENTS = 'etablissements-touristiques-lareunion-wssoubik';
  • Central module registry call: registerHospitalityTools(server) is invoked from registerAllTools().
    registerHospitalityTools(server);
Behavior3/5

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

No annotations are present, so the description carries full burden. It lists the fields returned but does not explicitly state read-only nature, rate limits, or pagination behavior (though limit parameter is documented in schema). The description adds some behavioral context but could be more comprehensive.

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?

Two sentences plus an embedded list of return fields. The first sentence is somewhat long but effectively communicates scope. No unnecessary words. Well-structured and easy to parse.

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 search tool with 5 optional parameters and no output schema, the description covers the search domain, return fields, and provides a sibling reference. Could mention sorting behavior or free-text query capabilities, but overall sufficiently complete for an agent to use 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 description coverage is 100%, so baseline is 3. The description does not add additional detail beyond what is already in the schema's parameter descriptions. It reiterates examples but does not enhance understanding of parameter semantics.

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?

Description clearly states the tool searches the SIT Soubik catalog for La Réunion tourism establishments, lists the types of establishments included, and specifies the fields returned. It also explicitly distinguishes from a sibling tool (reunion_search_classified_accommodations) by noting when to use that alternative.

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?

Provides clear context: it is for searching tourism establishments in La Réunion with various filters. Explicitly tells the agent when to use an alternative tool (for star-classified accommodations). However, it does not cover when not to use this tool versus other tourism-related tools like reunion_list_hiking_circuits.

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