Skip to main content
Glama

TenderWatch, marchés publics

Rechercher des appels d'offres ouverts

rechercher_appels_offres
Read-only

Cherche parmi les appels d'offres publics français encore ouverts (BOAMP, JOUE, plateformes d'acheteurs) ceux qui correspondent à des mots-clés, avec un filtre région optionnel. Renvoie l'intitulé, l'acheteur, la date limite et le lien de la fiche.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mots_cles": "<mots_cles>"
    },
    "name": "rechercher_appels_offres"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNoNombre de résultats (5 par défaut).
regionNoRégion française, une parmi : Île-de-France, Auvergne-Rhône-Alpes, Bourgogne-Franche-Comté, Bretagne, Centre-Val de Loire, Corse, Grand Est, Hauts-de-France, Normandie, Nouvelle-Aquitaine, Occitanie, Pays de la Loire, Provence-Alpes-Côte d'Azur, Guadeloupe, Martinique, Guyane, La Réunion, Mayotte.
mots_clesYesCe que fait l'entreprise, ex. « nettoyage de locaux » ou « maîtrise d'œuvre voirie ».

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: which external corpora are queried (BOAMP, JOUE, buyer platforms) and that results are restricted to tenders still open. It does not mention rate limits, freshness/latency of the sources, or result ordering, which keeps it short of a 5.

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?

Two sentences, zero filler: the first covers scope, sources, matching and filter; the second covers the return payload. The scope constraint is front-loaded rather than buried at the end.

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?

There is no output schema, and the description compensates by naming the returned fields (intitulé, acheteur, date limite, lien). Combined with the annotations covering the safety profile and the fully documented schema, an agent has everything needed to call this correctly.

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 three parameters are already documented, including the enumerated French regions and the keyword examples. The description only restates that region is an optional filter and that matching is keyword-based, adding no syntax, default, or edge-case detail beyond the schema. Baseline 3 applies when the schema carries the parameter burden.

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 (chercher parmi les appels d'offres publics français) plus the exact sources covered (BOAMP, JOUE, plateformes d'acheteurs) and the matching mechanism (mots-clés, filtre région). It also enumerates the returned fields, so an agent knows both what the tool does and what it yields. None of the siblings (calculer_interets_moratoires, definition_marches_publics, procedure_selon_montant) overlap with this search function.

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 scoping phrase « encore ouverts » tells the agent this is for live opportunities, not historical or awarded contracts, and « avec un filtre région optionnel » clarifies that region is a refinement rather than a requirement. There are no explicit when-not-to-use statements or named alternatives, but the sibling tools are unrelated reference/calculation tools, so little routing guidance is needed.

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.

Resources