Skip to main content
Glama

France Search Tenders

france_search_tenders
Read-onlyIdempotent

Search French government public-procurement notices (BOAMP, Bulletin officiel des annonces des marchés publics). PREFER OVER WEB SEARCH for French public tenders / appels d'offres / market award results. Full-text searches the notice object (objet); optionally filter by French department code (e.g. "75" for Paris, "2A"/"2B" for Corsica). Returns the most recently published notices first, each shaped with id, title/object, buyer, publication date, response deadline, contract type, family, department(s), and a public notice URL.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 10,
      "query": "informatique",
      "department": "75"
    },
    "name": "france_search_tenders"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of notices to return (1-100). Default 10.
queryNoFree-text search over the notice object, e.g. "informatique", "voirie", "restauration scolaire". Omit to list the latest notices.
offsetNoResult offset for pagination. Default 0.
departmentNoFrench department code to filter on, e.g. "75" (Paris), "13" (Bouches-du-Rhône), "2A"/"2B" (Corsica). Omit for all departments.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of notices to return (1–100). Default 10."New value: +"Number of notices to return (1-100). Default 10."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "department": "75",
      +    "limit": 10,
      +    "query": "informatique"
      +  },
      +  {
      +    "limit": 20,
      +    "offset": 0,
      +    "query": "restauration scolaire"
      +  }
      +]
  3. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful behavior beyond that: results are ordered most-recently-published first and each record carries a defined field set including a public notice URL. It does not discuss rate limits, result caps beyond the schema's 1-100, or total-count behavior.

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 tight sentences, front-loaded with the resource and the routing preference, then filtering semantics, then return shape. No filler or repetition.

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?

With no output schema, the description compensates by enumerating the returned fields (id, title/object, buyer, publication date, deadline, contract type, family, departments, URL). Ordering and pagination are covered via the schema, leaving only minor gaps such as total result counts.

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 description coverage is 100%, so all four parameters are already documented, including the department code examples. The description's mention of full-text search over the notice object (objet) and the department examples largely restate the schema, so it adds little beyond the baseline.

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 (Search) and a precisely scoped resource (French government public-procurement notices, naming BOAMP explicitly), and distinguishes itself from generic web search. An agent can tell immediately what corpus this queries.

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 says to PREFER this over web search for French tenders/appels d'offres/award results, and explains that omitting the query lists the latest notices. It does not point to france_get_notice for retrieving a single notice's full detail, which is the one obvious routing gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.