Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_search_possession_health_pros

Find health professionals in La Possession with per-act fees, OPTAM rates, and reimbursement base to estimate out-of-pocket costs.

Instructions

Search health professionals practicing specifically in La Possession (commune in west Réunion), with posted fees per technical act. Unlike reunion_search_health_professionals which is directory-only, this returns the typical price per act, the secteur 1 OPTAM/OPTAM-CO rate, the off-OPTAM rate, and the social security reimbursement base. Useful to estimate out-of-pocket costs. Source: open data Mairie de La Possession via data.regionreunion.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
professionNoProfession prefix match. Examples: "Médecin", "Dentiste", "Kinésithérapeute"
act_familyNoTechnical-act family prefix match. Examples: "Consultation", "Soins dentaires", "Imagerie"
conventionNoConvention status prefix. Examples: "Secteur 1", "Secteur 2", "Non conventionné"
limitNoMax rows to return (1-300, default 50)

Implementation Reference

  • The handler function for the 'reunion_search_possession_health_pros' tool. It queries the 'professionnels-de-sante-a-la-possession' dataset on OpenDataSoft (data.regionreunion.com), filters by profession, act_family, and convention, and returns professional details including name, address, phone, convention status, act details, typical fee amounts, and reimbursement base.
    server.tool(
      'reunion_search_possession_health_pros',
      'Search health professionals practicing specifically in La Possession (commune in west Réunion), with posted fees per technical act. Unlike reunion_search_health_professionals which is directory-only, this returns the typical price per act, the secteur 1 OPTAM/OPTAM-CO rate, the off-OPTAM rate, and the social security reimbursement base. Useful to estimate out-of-pocket costs. Source: open data Mairie de La Possession via data.regionreunion.com.',
      {
        profession: z.string().optional().describe('Profession prefix match. Examples: "Médecin", "Dentiste", "Kinésithérapeute"'),
        act_family: z.string().optional().describe('Technical-act family prefix match. Examples: "Consultation", "Soins dentaires", "Imagerie"'),
        convention: z.string().optional().describe('Convention status prefix. Examples: "Secteur 1", "Secteur 2", "Non conventionné"'),
        limit: z.number().int().min(1).max(300).default(50).describe('Max rows to return (1-300, default 50)'),
      },
      async ({ profession, act_family, convention, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_POSSESSION_PROS, {
            where: buildWhere([
              profession ? `profession LIKE ${quote(`${profession}%`)}` : undefined,
              act_family ? `famille_de_l_acte_technique_realise LIKE ${quote(`${act_family}%`)}` : undefined,
              convention ? `convention_et_cas LIKE ${quote(`${convention}%`)}` : undefined,
            ]),
            limit,
          });
          return jsonResult({
            total_rows: data.total_count,
            professionals: data.results.map((row) => ({
              name: pickString(row, ['nom_du_professionnel']),
              title: pickString(row, ['civilite']),
              profession: pickString(row, ['profession']),
              address: pickString(row, ['adresse']),
              commune: pickString(row, ['commune']),
              phone: pickString(row, ['numero_de_telephone']),
              convention: pickString(row, ['convention_et_cas']),
              sesam_vitale: pickString(row, ['sesam_vitale']),
              act_family: pickString(row, ['famille_de_l_acte_technique_realise']),
              act: pickString(row, ['acte_technique_realise']),
              typical_amount_eur: pickNumber(row, ['montant_generalement_constate']),
              sector_1_rate_eur: pickNumber(row, ['tarif_secteur_1_adherent_optam_optam_co']),
              off_sector_1_rate_eur: pickNumber(row, ['tarif_hors_secteur_1_hors_adherent_optam_optam_co']),
              reimbursement_base_eur: pickNumber(row, ['base_de_remboursement']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search Possession health pros');
        }
      }
    );
  • Input schema (validation) for the tool using Zod: profession (string, optional prefix match), act_family (string, optional prefix match), convention (string, optional prefix match), limit (integer 1-300, default 50).
    {
      profession: z.string().optional().describe('Profession prefix match. Examples: "Médecin", "Dentiste", "Kinésithérapeute"'),
      act_family: z.string().optional().describe('Technical-act family prefix match. Examples: "Consultation", "Soins dentaires", "Imagerie"'),
      convention: z.string().optional().describe('Convention status prefix. Examples: "Secteur 1", "Secteur 2", "Non conventionné"'),
      limit: z.number().int().min(1).max(300).default(50).describe('Max rows to return (1-300, default 50)'),
    },
  • The tool is registered via the McpServer.tool() call inside registerHealthTools(), which is called from src/modules/index.ts line 44. The tool name is 'reunion_search_possession_health_pros' with description about searching La Possession health professionals with posted fees.
    server.tool(
      'reunion_search_possession_health_pros',
      'Search health professionals practicing specifically in La Possession (commune in west Réunion), with posted fees per technical act. Unlike reunion_search_health_professionals which is directory-only, this returns the typical price per act, the secteur 1 OPTAM/OPTAM-CO rate, the off-OPTAM rate, and the social security reimbursement base. Useful to estimate out-of-pocket costs. Source: open data Mairie de La Possession via data.regionreunion.com.',
      {
        profession: z.string().optional().describe('Profession prefix match. Examples: "Médecin", "Dentiste", "Kinésithérapeute"'),
        act_family: z.string().optional().describe('Technical-act family prefix match. Examples: "Consultation", "Soins dentaires", "Imagerie"'),
        convention: z.string().optional().describe('Convention status prefix. Examples: "Secteur 1", "Secteur 2", "Non conventionné"'),
        limit: z.number().int().min(1).max(300).default(50).describe('Max rows to return (1-300, default 50)'),
      },
      async ({ profession, act_family, convention, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_POSSESSION_PROS, {
            where: buildWhere([
              profession ? `profession LIKE ${quote(`${profession}%`)}` : undefined,
              act_family ? `famille_de_l_acte_technique_realise LIKE ${quote(`${act_family}%`)}` : undefined,
              convention ? `convention_et_cas LIKE ${quote(`${convention}%`)}` : undefined,
            ]),
            limit,
          });
          return jsonResult({
            total_rows: data.total_count,
            professionals: data.results.map((row) => ({
              name: pickString(row, ['nom_du_professionnel']),
              title: pickString(row, ['civilite']),
              profession: pickString(row, ['profession']),
              address: pickString(row, ['adresse']),
              commune: pickString(row, ['commune']),
              phone: pickString(row, ['numero_de_telephone']),
              convention: pickString(row, ['convention_et_cas']),
              sesam_vitale: pickString(row, ['sesam_vitale']),
              act_family: pickString(row, ['famille_de_l_acte_technique_realise']),
              act: pickString(row, ['acte_technique_realise']),
              typical_amount_eur: pickNumber(row, ['montant_generalement_constate']),
              sector_1_rate_eur: pickNumber(row, ['tarif_secteur_1_adherent_optam_optam_co']),
              off_sector_1_rate_eur: pickNumber(row, ['tarif_hors_secteur_1_hors_adherent_optam_optam_co']),
              reimbursement_base_eur: pickNumber(row, ['base_de_remboursement']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search Possession health pros');
        }
      }
    );
  • buildWhere helper used to construct the ODSQL WHERE clause from filter conditions.
    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;
    }
  • quote helper used to safely quote string literals for ODSQL queries.
    export function quote(value: string): string {
      return `'${escapeOdSqlString(value)}'`;
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It describes return fields but does not disclose data freshness, pagination, rate limits, or side effects. As a search tool, it is implicitly read-only, but lacks explicit behavioral details.

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?

Three concise sentences front-loaded with purpose, contrasts with sibling, and includes source. No redundant information; every sentence adds value.

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 no output schema, description adequately explains what the tool returns (fees, rates, reimbursement base) and its data source. Covers purpose, usage, and output, making it complete for an agent to decide and invoke.

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 covers 100% of parameters with descriptions. The description adds context about return fields relating to parameters (e.g., fees per act) but does not provide additional parameter-level semantics beyond schema.

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 it searches health professionals in La Possession with fees per act, and explicitly distinguishes from reunion_search_health_professionals. Uses specific verb 'search' and defines unique resource 'health professionals in La Possession with posted fees'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit contrast with sibling tool reunion_search_health_professionals, stating when to use this tool (to estimate costs) versus when to use the sibling (directory-only). Also mentions practical use: estimating out-of-pocket costs.

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