Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_search_classified_accommodations

Find accommodations in La Réunion with official Atout France star classification. Filter by typology, star rating, or commune to locate hotels, campsites, and holiday villages.

Instructions

Search collective accommodations in La Réunion that hold an official Atout France star classification (1 to 5 étoiles, valid 5 years). Covers hôtels de tourisme, résidences de tourisme, campings, villages de vacances, parcs résidentiels de loisirs. Returns commercial name, typology, classification (stars), category, classification date and extension flag, stay type, commune, postal code, address, website, room count, capacity in persons. Sorted by classification date descending. Source: Atout France via data.regionreunion.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typologyNoTypology prefix match. Examples: "Hôtel de tourisme", "Camping", "Résidence de tourisme", "Village de vacances", "Parc résidentiel de loisirs"
classificationNoStar classification prefix match. Examples: "1 étoile", "2 étoiles", "3 étoiles", "4 étoiles", "5 étoiles"
communeNoCommune name prefix match
limitNoMax accommodations to return (1-300, default 50)

Implementation Reference

  • Registration of the 'reunion_search_classified_accommodations' tool via server.tool() call within the registerHospitalityTools function, at line 54.
    );
    
    server.tool(
  • Async handler function for the tool. Queries the 'hebergements-classespublic' OpenDataSoft dataset with filters, sorts by classification date descending, and maps results to a structured response.
      async ({ typology, classification, commune, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_CLASSIFIED, {
            where: buildWhere([
              typology ? `typologie_etablissement LIKE ${quote(`${typology}%`)}` : undefined,
              classification ? `classement LIKE ${quote(`${classification}%`)}` : undefined,
              commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
            ]),
            order_by: 'date_de_classement DESC',
            limit,
          });
          return jsonResult({
            total_accommodations: data.total_count,
            accommodations: data.results.map((row) => ({
              name: pickString(row, ['nom_commercial']),
              typology: pickString(row, ['typologie_etablissement']),
              classification: pickString(row, ['classement']),
              category: pickString(row, ['categorie']),
              classification_date: pickString(row, ['date_de_classement']),
              classification_extended: pickString(row, ['classement_proroge']),
              stay_type: pickString(row, ['type_de_sejour']),
              commune: pickString(row, ['commune']),
              postal_code: pickString(row, ['code_postal']),
              address: pickString(row, ['adresse']),
              website: pickString(row, ['site_internet']),
              room_count: pickNumber(row, ['nombre_de_chambres']),
              capacity_persons: pickString(row, ['capacite_d_accueil_personnes']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search classified accommodations');
        }
      }
    );
  • Input schema for the tool defined with Zod: optional typology, classification, commune (string) and limit (number, 1-300, default 50).
    {
      typology: z.string().optional().describe('Typology prefix match. Examples: "Hôtel de tourisme", "Camping", "Résidence de tourisme", "Village de vacances", "Parc résidentiel de loisirs"'),
      classification: z.string().optional().describe('Star classification prefix match. Examples: "1 étoile", "2 étoiles", "3 étoiles", "4 étoiles", "5 étoiles"'),
      commune: z.string().optional().describe('Commune name prefix match'),
      limit: z.number().int().min(1).max(300).default(50).describe('Max accommodations to return (1-300, default 50)'),
    },
  • Dataset identifier constant for the classified accommodations data source ('hebergements-classespublic').
    const DATASET_CLASSIFIED = 'hebergements-classespublic';
    const DATASET_ECOLODGE = 'localisation-potentielle-ecolodge-lareunion';
  • Registration entry point: registerHospitalityTools is imported from hospitality.ts and called in registerAllTools() to wire the tool into the MCP server.
    import { registerHospitalityTools } from './hospitality.js';
    import { registerHousingTools } from './housing.js';
    import { registerNationalElectionsTools } from './national-elections.js';
    import { registerPossessionTools } from './possession.js';
    import { registerSocialTools } from './social.js';
    import { registerTelecomTools } from './telecom.js';
    import { registerTerritoryTools } from './territory.js';
    import { registerTourismTools } from './tourism.js';
    import { registerTransportTools } from './transport.js';
    import { registerUrbanismTools } from './urbanism.js';
    import { registerWeatherTools } from './weather.js';
    
    export const TOOL_COUNT = 99;
    
    /**
     * Register all tool modules with the MCP server.
     */
    export function registerAllTools(server: McpServer): void {
      registerAdministrationTools(server);
      registerCatalogTools(server);
      registerCommuneTools(server);
      registerCultureTools(server);
      registerEconomyTools(server);
      registerEducationTools(server);
      registerEmploymentTools(server);
      registerEnvironmentTools(server);
      registerFacilityTools(server);
      registerGeographyTools(server);
      registerHealthTools(server);
      registerHospitalityTools(server);
      registerHousingTools(server);
      registerNationalElectionsTools(server);
      registerPossessionTools(server);
      registerSocialTools(server);
      registerTelecomTools(server);
      registerTerritoryTools(server);
      registerTourismTools(server);
      registerTransportTools(server);
      registerUrbanismTools(server);
      registerWeatherTools(server);
    }
Behavior4/5

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

With no annotations provided, the description carries full burden. It discloses sorting by classification date descending, the source (Atout France via data.regionreunion.com), and the scope of accommodations (specific typologies). It does not mention authentication or rate limits but is thorough otherwise.

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 description is a single dense paragraph but is front-loaded with purpose and covers all essentials without wasted words. Slightly more structure (e.g., bullet points for return fields) could improve readability, but it is concise and informative.

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?

Given the tool has no output schema, the description fully explains return values (commercial name, typology, classification, etc.), sorting, source, and scope. It also covers the limit parameter and types of accommodations. No gaps for the intended use case.

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 adds minimal extra meaning beyond the schema; it confirms parameters are prefix matches and provides context (e.g., 'typology prefix match'). No significant enrichment.

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 precisely states the tool searches for collective accommodations in La Réunion with official Atout France star classification, lists covered accommodation types, and details returned fields. It clearly distinguishes from sibling tools by focusing on classified accommodations.

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 description clearly indicates when to use the tool (searching for classified accommodations) and provides a comprehensive list of what it covers. It does not explicitly state when not to use or mention alternatives, but the sibling context implies the tool's specific niche.

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