Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_search_car_jaune_stops

Search bus stops of La Réunion's Car Jaune interurban bus network by name, code, or wheelchair accessibility. Returns stop details including coordinates and accessibility flags.

Instructions

Search bus stops of the Car Jaune network — La Réunion's interurban bus service operated by the Région — using GTFS data. Returns stop_id, stop_code, name, description, zone_id, location_type, parent_station, wheelchair-boarding flag, geographic coordinates. Use reunion_list_car_jaune_routes to list bus lines. Source: GTFS feed via data.regionreunion.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search on stop name (e.g. "Saint-Denis", "Aéroport", "Gare")
stop_codeNoExact stop code as displayed at the stop
wheelchair_accessibleNoIf true, return only stops flagged wheelchair-accessible (GTFS wheelchair_boarding = "1")
limitNoMax stops to return (1-500, default 50)

Implementation Reference

  • The tool handler for 'reunion_search_car_jaune_stops'. It defines the tool with an MCP server.tool() call, accepts query/stop_code/wheelchair_accessible/limit parameters validated via Zod, queries the OpenDataSoft GTFS dataset (DATASET_GTFS = 'donnees-gtfs-lareunion'), builds an ODSQL WHERE clause, and returns stop records with stop_id, stop_code, stop_name, stop_desc, zone_id, location_type, parent_station, wheelchair_boarding, and stop_coordinates.
    server.tool(
      'reunion_search_car_jaune_stops',
      'Search bus stops of the Car Jaune network — La Réunion\'s interurban bus service operated by the Région — using GTFS data. Returns stop_id, stop_code, name, description, zone_id, location_type, parent_station, wheelchair-boarding flag, geographic coordinates. Use reunion_list_car_jaune_routes to list bus lines. Source: GTFS feed via data.regionreunion.com.',
      {
        query: z.string().optional().describe('Free-text search on stop name (e.g. "Saint-Denis", "Aéroport", "Gare")'),
        stop_code: z.string().optional().describe('Exact stop code as displayed at the stop'),
        wheelchair_accessible: z.boolean().optional().describe('If true, return only stops flagged wheelchair-accessible (GTFS wheelchair_boarding = "1")'),
        limit: z.number().int().min(1).max(500).default(50).describe('Max stops to return (1-500, default 50)'),
      },
      async ({ query, stop_code, wheelchair_accessible, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_GTFS, {
            where: buildWhere([
              query ? `search(${quote(query)})` : undefined,
              stop_code ? `stop_code = ${quote(stop_code)}` : undefined,
              wheelchair_accessible ? `wheelchair_boarding = ${quote('1')}` : undefined,
            ]),
            limit,
          });
          return jsonResult({
            total_stops: data.total_count,
            stops: data.results.map((row) => ({
              stop_id: pickString(row, ['stop_id']),
              stop_code: pickString(row, ['stop_code']),
              stop_name: pickString(row, ['stop_name']),
              stop_desc: pickString(row, ['stop_desc']),
              zone_id: pickString(row, ['zone_id']),
              location_type: pickString(row, ['location_type']),
              parent_station: pickString(row, ['parent_station']),
              wheelchair_boarding: pickString(row, ['wheelchair_boarding']),
              stop_coordinates: row.stop_coordinates,
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to fetch Car Jaune stops');
        }
      }
    );
  • Zod schema for input validation: 'query' (optional string), 'stop_code' (optional string), 'wheelchair_accessible' (optional boolean), 'limit' (integer 1-500, default 50).
    {
      query: z.string().optional().describe('Free-text search on stop name (e.g. "Saint-Denis", "Aéroport", "Gare")'),
      stop_code: z.string().optional().describe('Exact stop code as displayed at the stop'),
      wheelchair_accessible: z.boolean().optional().describe('If true, return only stops flagged wheelchair-accessible (GTFS wheelchair_boarding = "1")'),
      limit: z.number().int().min(1).max(500).default(50).describe('Max stops to return (1-500, default 50)'),
    },
  • buildWhere helper constructs ODSQL WHERE clauses from conditions, used by the tool handler to filter stops by query, stop_code, and wheelchair_accessible.
    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;
    }
  • pickString helper extracts string values from API records, used to map raw API fields to output fields.
    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;
    }
  • registerAllTools() calls registerTransportTools(server) on line 53, which registers the 'reunion_search_car_jaune_stops' tool.
    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);
    }
Behavior3/5

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

With no annotations, description carries full burden. It lists returned fields (stop_id, name, etc.) and mentions GTFS data source, but does not disclose other behavioral traits like idempotency, rate limits, or authentication. No contradictions.

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?

Description is two sentences: first sentence states purpose and context, second adds return fields, sibling reference, and source. No filler, front-loaded info.

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?

Given the simple tool (4 optional params, no output schema), the description covers purpose, return fields, data source, and related tool. Minor addition could be coordinate format but overall complete.

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 schema descriptions are quite detailed (e.g., 'Free-text search on stop name'). The description adds no additional semantic meaning beyond what the schema already provides.

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 'Search bus stops of the Car Jaune network' with specific resource (bus stops) and operator (La Réunion's interurban bus service). It distinguishes from sibling tools by referencing Car Jaune specifically and recommending reunion_list_car_jaune_routes for listing lines.

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?

Explicitly directs users to reunion_list_car_jaune_routes for listing bus lines, providing an alternative. However, it does not explicitly state when not to use this tool or cover other siblings.

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