Skip to main content
Glama

France Boamp

by io.github.pipeworx-io
OverviewAdmin

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.

Input Schema

TableJSON 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. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "department": "75",
+    "limit": 10,
+    "query": "informatique"
+  },
+  {
+    "limit": 20,
+    "offset": 0,
+    "query": "restauration scolaire"
+  }
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds fine-grained behavior: full-text search on 'objet', optional department filter, sorted by most recent first, and specifies return fields (id, title, buyer, dates, etc.). No contradictions.

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?

The description is compact (~80 words), front-loaded with purpose and guidance, then specific parameters and return format. Every sentence adds value; 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?

Given the tool's complexity (4 params, no required, no output schema), the description covers all essential aspects: what it does, when to use, parameters, filtering, sorting, and return structure. It provides sufficient context for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with good descriptions. The tool description provides additional context like examples ('informatique', '75') and explains behavior when parameters are omitted (e.g., query omitted lists latest). This enriches understanding 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 the tool searches French government procurement notices (BOAMP) and distinguishes itself from sibling 'france_get_notice' by being a search function. It also explicitly prefers this tool over web search for French tenders.

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 advises to prefer this tool over web search and explains when to omit query for latest notices. It does not fully exclude other tools like france_get_notice, but the guidance is clear and actionable.

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

All France Boamp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources