Skip to main content
Glama

PublicOffre — marchés publics français

Rechercher des appels d’offres publics ouverts

rechercher_appels_offres
Read-onlyIdempotent

Appels d’offres publics ouverts en France (BOAMP, JOUE/TED, plateformes publiques), mis à jour chaque jour : objet, acheteur, date limite, lieu, lien. Filtrer par mots-clés, département (ex. 69, 2A, 974) et métier (division CPV à 2 chiffres, ex. 45 travaux, 72 informatique, 90 nettoyage, 77 espaces verts, 71 ingénierie).

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": "rechercher_appels_offres"
  }
}

Input Schema

NameRequiredDescriptionDefault
limiteNo
mots_clesNoMots de l’objet, ex. « nettoyage des locaux »
departementNoCode du département, ex. 69
division_cpvNoDivision CPV à 2 chiffres, ex. 45

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds useful context beyond annotations: source coverage, daily updates, and the fields returned. It does not mention rate limits, pagination, or the effect of the limit parameter.

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 two compact, front-loaded sentences with no filler. The source list, return fields, and filter examples all earn their place.

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 usefully names the returned fields, sources, and update frequency, which covers most of what an agent needs. It leaves out limit behavior and explicit routing to sibling tools, so it is strong but not fully complete.

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 description coverage is 75%, and the description adds concrete meaning for the filters, especially department code formats (2A, 974) and CPV division examples with domain mappings. It does not explain the limite parameter, but that parameter has schema min/max constraints.

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 states a specific resource and scope: open public tenders in France from BOAMP, JOUE/TED, and public platforms. It also names the returned fields and filters, so an agent can distinguish it from siblings such as qui_remporte_les_marches by the focus on open tenders rather than awarded contracts.

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?

The description clearly implies the tool is for searching open tenders and lists filter dimensions, but it does not explicitly say when to use it versus alternatives like concurrence_marches_publics or qui_remporte_les_marches. No exclusions or sibling routing are provided.

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