Skip to main content
Glama

Search Official Registry & Tender Records

search_tenders
Read-onlyIdempotent

Search France and EU official registries for public tenders, contract awards, grants, and commercial notices using keywords, dates, sections, and notice types.

Instructions

Run full-text and structured searches across indexed France and EU official registries (BODACC commercial registry, BOAMP public tenders/awards, EU TED FRA, SEDIA, and EU FSF). Costs $0.10 USDC or EURC per call using DATAX_TOKEN (returns HTTP 402 payment instructions if unset or depleted; auto-rotates change_token in memory). Returns masked previews and opaque item_ref handles ('dx_...'); pass an item_ref to get_tender_detail ($0.50) to unlock full verbatim text, corporate IDs, and official URLs. Use find_funded_companies when filtering by EUR amounts/liquidity events or check_company_risk to screen a specific company (use datax-spain-eu-mcp for Spanish property auctions via find_distressed_auctions).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of matching records to return (1 to 25, default 10).
queryNoFull-text search keywords matched across notice titles, subjects, authorities, and body text (e.g. 'cloud infrastructure'). Optional when filtering by seccion, notice_type, or dates.
date_toNoInclusive upper publication date bound in YYYYMMDD format (e.g. '20261117').
seccionNoRegistry section filter: 'ALL' (default), 'PA' (contract awards), 'PC' (open tenders), 'BA'/'BB' (commercial registry), 'SA'/'SC' (grants), 'LC' (legislation), 'MV' (financial regulator), 'TE' (EU TED), 'EU' (EU SEDIA), 'SF' (EU sanctions), or BOE codes '1','2B','3','4','5A','5B','5C'.ALL
date_fromNoInclusive lower publication date bound in YYYYMMDD format (e.g. '20261110').
match_modeNoBoolean operator for multi-word queries: 'AND' requires all words (default), 'OR' matches any word.AND
notice_typeNoNotice classification filter: 'ALL' (default), 'LICITACION', 'FORMALIZACION', 'MODIFICACION', 'OPOSICION', 'SUBASTA', 'SUBVENCION', 'CONCESION', 'SANCION', 'ENERGIA_EXPROPIACION', 'NORMATIVA', 'CONSTITUCION', 'CONCURSO_DISOLUCION', 'MERCANTIL', or 'ANUNCIO'.ALL

Output Schema

NameRequiredDescriptionDefault
resultNo
statusNo
change_tokenNo
change_microsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv0.1.1
    • addedInput schema / properties / date_from / description
      Added value: +"Inclusive lower publication date bound in YYYYMMDD format (e.g. '20261110')."
    • addedInput schema / properties / date_from / pattern
      Added value: +"^\\d{8}$"
    • addedInput schema / properties / date_to / description
      Added value: +"Inclusive upper publication date bound in YYYYMMDD format (e.g. '20261117')."
    • addedInput schema / properties / date_to / pattern
      Added value: +"^\\d{8}$"
    • addedInput schema / properties / limit / default
      Added value: +10
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of matching records to return (1 to 25, default 10)."
    • addedInput schema / properties / limit / maximum
      Added value: +25
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / match_mode
      Added value: +{
      +  "default": "AND",
      +  "description": "Boolean operator for multi-word queries: 'AND' requires all words (default), 'OR' matches any word.",
      +  "enum": [
      +    "AND",
      +    "OR"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / notice_type / default
      Added value: +"ALL"
    • addedInput schema / properties / notice_type / description
      Added value: +"Notice classification filter: 'ALL' (default), 'LICITACION', 'FORMALIZACION', 'MODIFICACION', 'OPOSICION', 'SUBASTA', 'SUBVENCION', 'CONCESION', 'SANCION', 'ENERGIA_EXPROPIACION', 'NORMATIVA', 'CONSTITUCION', 'CONCURSO_DISOLUCION', 'MERCANTIL', or 'ANUNCIO'."
    • addedInput schema / properties / notice_type / enum
      Added value: +[
      +  "ALL",
      +  "LICITACION",
      +  "FORMALIZACION",
      +  "MODIFICACION",
      +  "OPOSICION",
      +  "SUBASTA",
      +  "SUBVENCION",
      +  "CONCESION",
      +  "SANCION",
      +  "ENERGIA_EXPROPIACION",
      +  "NORMATIVA",
      +  "CONSTITUCION",
      +  "CONCURSO_DISOLUCION",
      +  "MERCANTIL",
      +  "ANUNCIO"
      +]
    • addedInput schema / properties / query / description
      Added value: +"Full-text search keywords matched across notice titles, subjects, authorities, and body text (e.g. 'cloud infrastructure'). Optional when filtering by seccion, notice_type, or dates."
    • addedInput schema / properties / seccion / default
      Added value: +"ALL"
    • addedInput schema / properties / seccion / description
      Added value: +"Registry section filter: 'ALL' (default), 'PA' (contract awards), 'PC' (open tenders), 'BA'/'BB' (commercial registry), 'SA'/'SC' (grants), 'LC' (legislation), 'MV' (financial regulator), 'TE' (EU TED), 'EU' (EU SEDIA), 'SF' (EU sanctions), or BOE codes '1','2B','3','4','5A','5B','5C'."
    • addedInput schema / properties / seccion / enum
      Added value: +[
      +  "ALL",
      +  "1",
      +  "2B",
      +  "3",
      +  "4",
      +  "5A",
      +  "5B",
      +  "5C",
      +  "BA",
      +  "BB",
      +  "SA",
      +  "SC",
      +  "PC",
      +  "PA",
      +  "EU",
      +  "TE",
      +  "LC",
      +  "SF",
      +  "MV"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "change_micros": {
      +      "type": "integer"
      +    },
      +    "change_token": {
      +      "type": "string"
      +    },
      +    "result": {
      +      "properties": {
      +        "data_version": {
      +          "type": "string"
      +        },
      +        "matches": {
      +          "items": {
      +            "properties": {
      +              "ambito": {
      +                "description": "Geographic jurisdiction or region.",
      +                "type": "string"
      +              },
      +              "detail_locked": {
      +                "description": "Always true until unlocked with get_tender_detail.",
      +                "type": "boolean"
      +              },
      +              "fecha_pub": {
      +                "description": "Publication date in YYYYMMDD format.",
      +                "type": "string"
      +              },
      +              "importe_texto": {
      +                "description": "Formatted amount string when available.",
      +                "type": "string"
      +              },
      +              "item_ref": {
      +                "description": "Opaque encrypted record reference ('dx_...') for get_tender_detail.",
      +                "type": "string"
      +              },
      +              "notice_type": {
      +                "description": "Notice classification.",
      +                "type": "string"
      +              },
      +              "preview": {
      +                "description": "Redacted summary preview without PII or entity identifiers.",
      +                "type": "string"
      +              },
      +              "seccion": {
      +                "description": "Registry section code.",
      +                "type": "string"
      +              },
      +              "unlock_price_micros": {
      +                "description": "Unlock price in USD/EUR micros (500000 = 0.50).",
      +                "type": "integer"
      +              }
      +            },
      +            "type": "object"
      +          },
      +          "type": "array"
      +        },
      +        "operation": {
      +          "type": "string"
      +        },
      +        "total_returned": {
      +          "type": "integer"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/open-world safety; the description adds substantial context beyond them — per-call pricing ($0.10 USDC or EURC), DATAX_TOKEN auth requirement, HTTP 402 payment-instruction behavior when unset or depleted, in-memory change_token rotation, and that results are masked previews requiring a separate $0.50 call to unlock. These are exactly the operational facts an agent needs before invoking.

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?

Purpose and sources are front-loaded, then cost/auth, then the get_tender_detail handoff and sibling routing — a logical order with no filler. It is dense with nested parentheticals and runs long, which costs a point, but every sentence contributes actionable information.

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?

For a zero-required-parameter search tool with an output schema, the description covers what matters: which corpora, cost and payment failure mode, result masking, and the follow-up call needed for full data. Nothing essential to correct invocation is missing.

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?

With 100% schema description coverage across all 7 parameters, the schema already carries the semantics (enums, date patterns, match_mode, limit bounds). The description adds little parameter-level detail beyond noting query supports full-text search and that filtering can be structured; baseline 3 applies.

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?

States a specific verb and resource ('Run full-text and structured searches') and enumerates the exact corpora searched (BODACC, BOAMP, EU TED FRA, SEDIA, EU FSF). It also implicitly separates itself from get_tender_detail by describing this tool as returning masked previews rather than full text.

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?

Explicitly routes the agent: pass an item_ref to get_tender_detail for full text, use find_funded_companies for EUR amount/liquidity filtering, check_company_risk to screen a company, and datax-spain-eu-mcp for Spanish property auctions. This is explicit when-to-use and when-to-use-something-else guidance, not inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.