Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_search_rge_companies

Locate RGE-certified companies in La Réunion, required for clients to qualify for energy-renovation state aids. Use free-text search or filter by commune and domain.

Instructions

Search companies certified RGE (Reconnu Garant de l'Environnement) in La Réunion. RGE certification is required for clients to qualify for state aids on energy-renovation work (MaPrimeRénov', éco-PTZ, CEE). Returns SIRET, company name, address, postal code, commune, phone, email, website, certification name, qualification, domain (insulation/heating/PV/...), meta-domain, certifying organization, lat/lon. Source: ADEME via data.regionreunion.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search across company name, address, certification
communeNoCommune name prefix match
domainNoSpecific domain prefix match. Examples: "Isolation", "Chauffage", "Photovoltaïque", "Eau chaude sanitaire", "Pompe à chaleur"
limitNoMax companies to return (1-100, default 25)

Implementation Reference

  • The MCP tool handler for 'reunion_search_rge_companies'. Defines the tool with name, description, input schema (query, commune, domain, limit), and the async handler function that queries the OpenDataSoft API (dataset 'liste-des-entreprises-rge-2') and maps results to a structured JSON response with company fields (SIRET, name, address, commune, phone, email, website, certification, qualification, domain, meta-domain, lat/lon).
    server.tool(
      'reunion_search_rge_companies',
      'Search companies certified RGE (Reconnu Garant de l\'Environnement) in La Réunion. RGE certification is required for clients to qualify for state aids on energy-renovation work (MaPrimeRénov\', éco-PTZ, CEE). Returns SIRET, company name, address, postal code, commune, phone, email, website, certification name, qualification, domain (insulation/heating/PV/...), meta-domain, certifying organization, lat/lon. Source: ADEME via data.regionreunion.com.',
      {
        query: z.string().optional().describe('Free-text search across company name, address, certification'),
        commune: z.string().optional().describe('Commune name prefix match'),
        domain: z.string().optional().describe('Specific domain prefix match. Examples: "Isolation", "Chauffage", "Photovoltaïque", "Eau chaude sanitaire", "Pompe à chaleur"'),
        limit: z.number().int().min(1).max(100).default(25).describe('Max companies to return (1-100, default 25)'),
      },
      async ({ query, commune, domain, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_RGE_COMPANIES, {
            where: buildWhere([
              query ? `search(${quote(query)})` : undefined,
              commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
              domain ? `domaine LIKE ${quote(`${domain}%`)}` : undefined,
            ]),
            limit,
          });
          return jsonResult({
            total_companies: data.total_count,
            companies: data.results.map((row) => ({
              siret: pickString(row, ['siret']),
              name: pickString(row, ['nom_entreprise']),
              address: pickString(row, ['adresse']),
              postal_code: pickString(row, ['code_postal']),
              commune: pickString(row, ['commune']),
              phone: pickString(row, ['telephone']),
              email: pickString(row, ['email']),
              website: pickString(row, ['site_internet']),
              certification: pickString(row, ['nom_certificat']),
              qualification: pickString(row, ['nom_qualification']),
              domain: pickString(row, ['domaine']),
              meta_domain: pickString(row, ['meta_domaine']),
              organization: pickString(row, ['organisme']),
              lat: pickNumber(row, ['latitude']),
              lon: pickNumber(row, ['longitude']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search RGE companies');
        }
      }
    );
  • Input schema for the tool: optional free-text query, optional commune prefix, optional domain prefix, and limit (1-100, default 25) defined using Zod.
    {
      query: z.string().optional().describe('Free-text search across company name, address, certification'),
      commune: z.string().optional().describe('Commune name prefix match'),
      domain: z.string().optional().describe('Specific domain prefix match. Examples: "Isolation", "Chauffage", "Photovoltaïque", "Eau chaude sanitaire", "Pompe à chaleur"'),
      limit: z.number().int().min(1).max(100).default(25).describe('Max companies to return (1-100, default 25)'),
    },
  • The tool is registered via McpServer.tool() in the registerEnvironmentTools function. This is called from src/modules/index.ts which is invoked from src/index.ts main().
    server.tool(
      'reunion_search_rge_companies',
      'Search companies certified RGE (Reconnu Garant de l\'Environnement) in La Réunion. RGE certification is required for clients to qualify for state aids on energy-renovation work (MaPrimeRénov\', éco-PTZ, CEE). Returns SIRET, company name, address, postal code, commune, phone, email, website, certification name, qualification, domain (insulation/heating/PV/...), meta-domain, certifying organization, lat/lon. Source: ADEME via data.regionreunion.com.',
      {
        query: z.string().optional().describe('Free-text search across company name, address, certification'),
        commune: z.string().optional().describe('Commune name prefix match'),
        domain: z.string().optional().describe('Specific domain prefix match. Examples: "Isolation", "Chauffage", "Photovoltaïque", "Eau chaude sanitaire", "Pompe à chaleur"'),
        limit: z.number().int().min(1).max(100).default(25).describe('Max companies to return (1-100, default 25)'),
      },
      async ({ query, commune, domain, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_RGE_COMPANIES, {
            where: buildWhere([
              query ? `search(${quote(query)})` : undefined,
              commune ? `commune LIKE ${quote(`${commune}%`)}` : undefined,
              domain ? `domaine LIKE ${quote(`${domain}%`)}` : undefined,
            ]),
            limit,
          });
          return jsonResult({
            total_companies: data.total_count,
            companies: data.results.map((row) => ({
              siret: pickString(row, ['siret']),
              name: pickString(row, ['nom_entreprise']),
              address: pickString(row, ['adresse']),
              postal_code: pickString(row, ['code_postal']),
              commune: pickString(row, ['commune']),
              phone: pickString(row, ['telephone']),
              email: pickString(row, ['email']),
              website: pickString(row, ['site_internet']),
              certification: pickString(row, ['nom_certificat']),
              qualification: pickString(row, ['nom_qualification']),
              domain: pickString(row, ['domaine']),
              meta_domain: pickString(row, ['meta_domaine']),
              organization: pickString(row, ['organisme']),
              lat: pickNumber(row, ['latitude']),
              lon: pickNumber(row, ['longitude']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search RGE companies');
        }
      }
    );
  • Helper buildWhere used to construct the ODSQL WHERE clause from optional conditions (query, commune, domain).
    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;
    }
  • Dataset ID constant DATASET_RGE_COMPANIES = 'liste-des-entreprises-rge-2' which points to the ADEME RGE companies dataset on data.regionreunion.com.
    const DATASET_RGE_COMPANIES = 'liste-des-entreprises-rge-2';
    const DATASET_ZNIEFF = 'zones-naturelles-d-interet-ecologique-faunistique-et-floristique-a-la-reunion';
    const DATASET_PNRUN = 'pnrun_2021';
    const DATASET_PETROLEUM = 'donnees-locales-de-consommation-de-produits-petroliers-a-la-reunion';
    const DATASET_WATER_POIS = 'les-points-d-activite-ou-d-interet-la-gestion-des-eaux';
Behavior4/5

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

With no annotations, the description bears full burden. It discloses the search behavior, returned fields (including geolocation and certification details), and data source. No contradictions; it adequately informs about the tool's read-only nature.

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 paragraph front-loaded with purpose and context. It is informative without being verbose, though slight conciseness could be improved.

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?

Without an output schema, the description lists all returned fields and explains the certification's importance. It provides sufficient context for usage, including data source and application.

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%, so the schema already documents parameters. The description adds domain examples but does not fundamentally extend meaning beyond schema. Baseline 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 the tool searches for RGE-certified companies in La Réunion, with a specific verb+resource+scope. It distinguishes itself from siblings by focusing on RGE certification and energy-renovation context.

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 explains when to use (when clients need state aids) and provides contextual background on RGE relevance. It lacks explicit 'when not to use' or alternatives, but the context is clear given sibling tools cover different domains.

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