Skip to main content
Glama
Hug0x0

mcp-reunion

reunion_search_boamp

Search public procurement notices for La Réunion from BOAMP. Retrieve open tenders, contract awards, and framework agreements with buyer, awardee, and deadline details.

Instructions

Search the BOAMP (Bulletin Officiel des Annonces de Marchés Publics) for public-procurement notices concerning La Réunion: open tenders (appels d'offres ouverts/restreints), MAPA (procédures adaptées), contract awards (avis d'attribution), framework agreements (accords-cadres), and concession contracts. Returns notice ID, web ID, object/description, buyer name, awardee (if any), procurement family/nature, procedure type and label, publication date, response deadline, status, official BOAMP URL. Sorted by publication date descending. Source: DILA / BOAMP via data.regionreunion.com.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoFree-text search across notice object, buyer, awardee, descriptions
buyerNoBuyer / contracting authority name prefix match. Examples: "Région Réunion", "Mairie de Saint-Denis", "CHU"
procedure_typeNoProcedure category prefix match. Examples: "Appel d'offres ouvert", "Procédure adaptée (MAPA)", "Marché négocié"
limitNoMax notices to return (1-100, default 25)

Implementation Reference

  • Async handler function that executes the reunion_search_boamp tool logic: queries the BOAMP dataset via the API client, builds WHERE filters from optional query/buyer/procedure_type parameters, orders by publication date descending, and maps results to structured notice objects (id, web_id, object, buyer, awardee, family_label, procedure_type, procedure_label, procedure_category, nature, sub_nature, published_at, response_deadline, state, url).
      async ({ query, buyer, procedure_type, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_BOAMP, {
            where: buildWhere([
              query ? `search(${quote(query)})` : undefined,
              buyer ? `nomacheteur LIKE ${quote(`${buyer}%`)}` : undefined,
              procedure_type ? `procedure_categorise LIKE ${quote(`${procedure_type}%`)}` : undefined,
            ]),
            order_by: 'dateparution DESC',
            limit,
          });
          return jsonResult({
            total_notices: data.total_count,
            notices: data.results.map((row) => ({
              id: pickString(row, ['id']),
              web_id: pickString(row, ['idweb']),
              object: pickString(row, ['objet']),
              buyer: pickString(row, ['nomacheteur']),
              awardee: pickString(row, ['titulaire']),
              family_label: pickString(row, ['famille_libelle']),
              procedure_type: pickString(row, ['type_procedure']),
              procedure_label: pickString(row, ['procedure_libelle']),
              procedure_category: pickString(row, ['procedure_categorise']),
              nature: pickString(row, ['nature_libelle']),
              sub_nature: pickString(row, ['sousnature_libelle']),
              published_at: pickString(row, ['dateparution']),
              response_deadline: pickString(row, ['datelimitereponse']),
              state: pickString(row, ['etat']),
              url: pickString(row, ['url_avis']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search BOAMP');
        }
      }
    );
  • Schema definition for the reunion_search_boamp tool: optional 'query' (free-text), 'buyer' (contracting authority name prefix), 'procedure_type' (procedure category prefix), and 'limit' (1-100, default 25) parameters with Zod validation.
    {
      query: z.string().optional().describe('Free-text search across notice object, buyer, awardee, descriptions'),
      buyer: z.string().optional().describe('Buyer / contracting authority name prefix match. Examples: "Région Réunion", "Mairie de Saint-Denis", "CHU"'),
      procedure_type: z.string().optional().describe('Procedure category prefix match. Examples: "Appel d\'offres ouvert", "Procédure adaptée (MAPA)", "Marché négocié"'),
      limit: z.number().int().min(1).max(100).default(25).describe('Max notices to return (1-100, default 25)'),
    },
  • Registration of the 'reunion_search_boamp' tool via server.tool() with description, schema, and handler. Exported via registerAdministrationTools() called from src/modules/index.ts.
    server.tool(
      'reunion_search_boamp',
      'Search the BOAMP (Bulletin Officiel des Annonces de Marchés Publics) for public-procurement notices concerning La Réunion: open tenders (appels d\'offres ouverts/restreints), MAPA (procédures adaptées), contract awards (avis d\'attribution), framework agreements (accords-cadres), and concession contracts. Returns notice ID, web ID, object/description, buyer name, awardee (if any), procurement family/nature, procedure type and label, publication date, response deadline, status, official BOAMP URL. Sorted by publication date descending. Source: DILA / BOAMP via data.regionreunion.com.',
      {
        query: z.string().optional().describe('Free-text search across notice object, buyer, awardee, descriptions'),
        buyer: z.string().optional().describe('Buyer / contracting authority name prefix match. Examples: "Région Réunion", "Mairie de Saint-Denis", "CHU"'),
        procedure_type: z.string().optional().describe('Procedure category prefix match. Examples: "Appel d\'offres ouvert", "Procédure adaptée (MAPA)", "Marché négocié"'),
        limit: z.number().int().min(1).max(100).default(25).describe('Max notices to return (1-100, default 25)'),
      },
      async ({ query, buyer, procedure_type, limit }) => {
        try {
          const data = await client.getRecords<RecordObject>(DATASET_BOAMP, {
            where: buildWhere([
              query ? `search(${quote(query)})` : undefined,
              buyer ? `nomacheteur LIKE ${quote(`${buyer}%`)}` : undefined,
              procedure_type ? `procedure_categorise LIKE ${quote(`${procedure_type}%`)}` : undefined,
            ]),
            order_by: 'dateparution DESC',
            limit,
          });
          return jsonResult({
            total_notices: data.total_count,
            notices: data.results.map((row) => ({
              id: pickString(row, ['id']),
              web_id: pickString(row, ['idweb']),
              object: pickString(row, ['objet']),
              buyer: pickString(row, ['nomacheteur']),
              awardee: pickString(row, ['titulaire']),
              family_label: pickString(row, ['famille_libelle']),
              procedure_type: pickString(row, ['type_procedure']),
              procedure_label: pickString(row, ['procedure_libelle']),
              procedure_category: pickString(row, ['procedure_categorise']),
              nature: pickString(row, ['nature_libelle']),
              sub_nature: pickString(row, ['sousnature_libelle']),
              published_at: pickString(row, ['dateparution']),
              response_deadline: pickString(row, ['datelimitereponse']),
              state: pickString(row, ['etat']),
              url: pickString(row, ['url_avis']),
            })),
          });
        } catch (error) {
          return errorResult(error instanceof Error ? error.message : 'Failed to search BOAMP');
        }
      }
    );
  • Imports of helper utilities used by the handler: buildWhere, errorResult, jsonResult, pickString, quote from '../utils/helpers.js'.
    import { buildWhere, errorResult, jsonResult, pickNumber, pickString, quote } from '../utils/helpers.js';
  • Dataset constant DATASET_BOAMP = 'boamp' defining the data source used by the reunion_search_boamp tool.
    const DATASET_BOAMP = 'boamp';
Behavior4/5

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

No annotations are provided, so the description carries full burden. It specifies return fields (notice ID, web ID, buyer, awardee, etc.) and sorting by publication date descending. It does not mention rate limits, authentication, or error handling, but the behavioral overview is adequate for a read-only search.

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?

One concise paragraph that front-loads the purpose, lists output fields efficiently, and ends with sorting and source information. Every sentence adds value with no redundancy.

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?

Even without an output schema, the description enumerates all return fields. It covers the tool's scope (public procurement notices in La Réunion), parameters, and behavior (sorted by date). No critical gaps identified.

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 has 4 parameters with full descriptions (100% coverage). The tool description does not add new parameter semantics beyond what is in the schema; it only provides examples that are already present. 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 the BOAMP for public procurement notices concerning La Réunion. It lists specific notice types (open tenders, MAPA, contract awards, etc.) and return fields, distinguishing it from many other search tools on the server.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives like reunion_possession_search_procurement, which may serve a similar purpose for a different geographic area. The description lacks 'when not to use' or context for selection among 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