Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_list_landmarks

List tourism landmarks in La Réunion: viewpoints, waterfalls, beaches, historical sites. Returns name, commune, major flag, UNESCO, and accessibility info. Ideal for travel guides and accessibility-aware itineraries.

Instructions

List remarkable tourism landmarks (lieux remarquables) in La Réunion from the SIT Soubik catalog: scenic viewpoints, waterfalls, beaches, cirque-belvédères, historical sites, etc. Returns landmark name, tagline (accroche), commune, "lieu majeur" flag (highlights), national-park flag, UNESCO World Heritage flag, characteristics, reduced-mobility accessibility. Useful for travel guides, must-see lists, accessibility-aware itineraries.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
communeNoCommune name prefix match
major_onlyNoIf true, return only landmarks flagged "lieu majeur" (top must-see sites)
limitNoMax landmarks to return (1-200, default 50)

Implementation Reference

  • The handler function that executes the 'reunion_list_landmarks' tool logic. It queries the OpenDataSoft API for landmarks from the 'lieux-remarquables-lareunion-wssoubik' dataset, applies optional filters (commune prefix, major_only), and maps results to a structured JSON response with fields like name, tagline, commune, major flag, national park flag, UNESCO flag, characteristics, and reduced mobility accessibility.
      async ({ commune, major_only, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_LANDMARKS, {
            where: buildWhere([
              commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
              major_only ? 'lieu_majeur = 1' : undefined,
            ]),
            limit,
          });
          return jsonResult({
            total_landmarks: data.total_count,
            landmarks: data.results.map((row) => ({
              name: pickString(row, ['nom_du_lieu_remarquable']),
              tagline: pickString(row, ['accroche']),
              commune: pickString(row, ['commune']),
              major: pickNumber(row, ['lieu_majeur']) === 1,
              in_national_park: pickNumber(row, ['situe_dans_un_parc_national']) === 1,
              unesco_world_heritage: pickNumber(row, ['appartient_au_patrimoine_mondial']) === 1,
              characteristics: pickString(row, ['caracteristiques']),
              reduced_mobility_accessible: pickString(row, ['accessible_mobilite_reduite']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to fetch landmarks');
        }
      }
    );
  • Input schema for the 'reunion_list_landmarks' tool using Zod. Parameters: commune (optional string, prefix match), major_only (boolean, default false), limit (integer 1-200, default 50).
    {
      commune: z.string().optional().describe('Commune name prefix match'),
      major_only: z.boolean().default(false).describe('If true, return only landmarks flagged "lieu majeur" (top must-see sites)'),
      limit: z.number().int().min(1).max(200).default(50).describe('Max landmarks to return (1-200, default 50)'),
    },
  • Registration of the 'reunion_list_landmarks' tool via server.tool() call, which defines the tool name, description, input schema, and handler function.
    server.tool(
      'reunion_list_landmarks',
      'List remarkable tourism landmarks (lieux remarquables) in La Réunion from the SIT Soubik catalog: scenic viewpoints, waterfalls, beaches, cirque-belvédères, historical sites, etc. Returns landmark name, tagline (accroche), commune, "lieu majeur" flag (highlights), national-park flag, UNESCO World Heritage flag, characteristics, reduced-mobility accessibility. Useful for travel guides, must-see lists, accessibility-aware itineraries.',
      {
        commune: z.string().optional().describe('Commune name prefix match'),
        major_only: z.boolean().default(false).describe('If true, return only landmarks flagged "lieu majeur" (top must-see sites)'),
        limit: z.number().int().min(1).max(200).default(50).describe('Max landmarks to return (1-200, default 50)'),
      },
      async ({ commune, major_only, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_LANDMARKS, {
            where: buildWhere([
              commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
              major_only ? 'lieu_majeur = 1' : undefined,
            ]),
            limit,
          });
          return jsonResult({
            total_landmarks: data.total_count,
            landmarks: data.results.map((row) => ({
              name: pickString(row, ['nom_du_lieu_remarquable']),
              tagline: pickString(row, ['accroche']),
              commune: pickString(row, ['commune']),
              major: pickNumber(row, ['lieu_majeur']) === 1,
              in_national_park: pickNumber(row, ['situe_dans_un_parc_national']) === 1,
              unesco_world_heritage: pickNumber(row, ['appartient_au_patrimoine_mondial']) === 1,
              characteristics: pickString(row, ['caracteristiques']),
              reduced_mobility_accessible: pickString(row, ['accessible_mobilite_reduite']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to fetch landmarks');
        }
      }
    );
  • The 'registerTourismTools' function that is exported and called from the index module to register all tourism tools including 'reunion_list_landmarks'.
    export function registerTourismTools(server: McpServer): void {
  • The buildWhere helper used to construct the ODSQL WHERE clause from optional conditions (commune filter and major_only filter).
    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;
    }
  • The pickString helper used to extract string values from record fields (e.g., name, tagline, commune, characteristics, accessibility).
    export function pickString(
      record: RecordObject,
      candidates: string[]
    ): string | undefined {
      const value = pickValue(record, candidates);
      if (typeof value === 'string') {
        return value;
      }
      if (typeof value === 'number' || typeof value === 'boolean') {
        return String(value);
      }
      return undefined;
    }
  • The pickNumber helper used to extract numeric values from record fields (e.g., lieu_majeur, situe_dans_un_parc_national, appartient_au_patrimoine_mondial).
    export function pickNumber(
      record: RecordObject,
      candidates: string[]
    ): number | undefined {
      const value = pickValue(record, candidates);
      if (typeof value === 'number' && Number.isFinite(value)) {
        return value;
      }
      if (typeof value === 'string' && value.trim() !== '') {
        const parsed = Number(value);
        return Number.isFinite(parsed) ? parsed : undefined;
      }
      return undefined;
    }
  • The quote helper used to safely quote string values in ODSQL WHERE clause conditions.
    export function quote(value: string): string {
      return `'${escapeOdSqlString(value)}'`;
    }
Behavior4/5

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

No annotations are provided, so the description bears full responsibility. It clearly describes what the tool returns (name, tagline, commune, flags for major, national park, UNESCO, reduced mobility accessibility), implying a read-only, informational operation with no destructive effects. However, it does not explicitly state it is read-only or mention any permissions needed.

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?

The description is concise, consisting of two sentences. The first sentence establishes the tool's purpose and source, and the second sentence lists output fields and use cases. No extraneous information; each sentence earns its place.

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?

Despite lacking an output schema, the description thoroughly enumerates the return fields (name, tagline, commune, flags, characteristics, accessibility). Given the tool's complexity (three optional parameters, no nested objects), the description is complete and provides sufficient context for an agent to use 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?

Input schema coverage is 100%, so the schema already documents all three parameters (commune, major_only, limit). The description does not add semantic value to the parameters beyond what the schema provides; it only lists output fields. Baseline score of 3 is appropriate.

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 clearly states that the tool lists remarkable tourism landmarks in La Réunion from the SIT Soubik catalog. It specifies the types of landmarks (scenic viewpoints, waterfalls, beaches, etc.) and the returned fields (name, tagline, commune, flags), effectively distinguishing it from sibling tools that focus on other data (e.g., museums, hiking circuits).

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 provides clear usage context, stating it is useful for 'travel guides, must-see lists, accessibility-aware itineraries.' While it does not explicitly exclude alternatives or state when not to use, it implicitly differentiates from sibling tools by focusing on landmarks; the context is sufficient.

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