Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

get_alimconfiance_etablissement

Recherche le score Alim'confiance d'un établissement précis dans le dataset officiel de la DGAL (export_alimconfiance, dgal.opendatasoft.com — 72 887 enregistrements). Retourne pour chaque inspection trouvée : score sanitaire (Très satisfaisant / Satisfaisant / À améliorer / À corriger de manière urgente), date du contrôle officiel, SIRET, enseigne, raison sociale, adresse complète, code postal, commune, type d'activité et numéro d'inspection. Recherche par SIRET (recommandé : identifiant unique et univoque) ou par nom d'enseigne avec filtre optionnel code postal et/ou commune pour désambiguïser. Données refreshées périodiquement par la DGAL ; couvre uniquement les établissements ayant fait l'objet d'un contrôle officiel depuis avril 2017.

[EN] Looks up a specific establishment's Alim'confiance inspection score in the official DGAL open dataset (real time): score, inspection date, SIRET, name, address. Search by 'siret' (recommended) or 'nom' + optional 'code_postal'/'commune'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nomNoNom commercial, enseigne ou raison sociale. Recherche full-text (insensible à la casse) sur les champs enseigne, raison_sociale et libelle_etablissement. Au moins 2 caractères requis. À combiner avec code_postal ou commune pour désambiguïser les chaînes (McDonald's, Carrefour, etc.).
limitNoNombre maximum de résultats à retourner (défaut 5, maximum 20). Les inspections les plus récentes en premier.
siretNoSIRET 14 chiffres de l'établissement. Recommandé pour une recherche directe et univoque. Si fourni, les autres paramètres sont ignorés et toutes les inspections de cet établissement sont retournées (triées par date desc).
communeNoNom de la commune (recherche full-text). Filtre additionnel pour désambiguïser une recherche par nom.
code_postalNoCode postal exact (5 chiffres) de l'établissement. Filtre additionnel pour désambiguïser une recherche par nom.

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It discloses dataset size, refresh cycle, coverage since April 2017, and parameter precedence (SIRET overrides others). This fully informs the agent of behavioral traits.

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?

The description is front-loaded with purpose and well-structured in two paragraphs plus an English version. While the bilingual repetition adds length, every sentence contributes useful information. Could be slightly more concise.

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 no output schema and no annotations, the description thoroughly covers search behavior, return fields, data source, and limitations. It leaves no critical gaps for an agent to invoke the tool 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 baseline is 3. The description repeats some schema details (e.g., SIRET uniqueness, full-text search on nom) without adding significant new semantics. It provides minimal extra value beyond the 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 explicitly states the tool's purpose: searching for an establishment's Alim'confiance score. It lists specific return fields (score, date, SIRET, etc.) and distinguishes the search modes, making it clear what resource is accessed.

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 recommends using SIRET for direct searches and explains when to combine nom with code_postal or commune to disambiguate. It does not explicitly contrast with sibling tools like get_score_alimconfiance, but provides sufficient context for effective use.

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.

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes, but there is potential confusion between get_haccp_temperatures and get_temperatures_cuisson (both about temperatures, but one storage/cooling, one cooking) and between get_rappels_produits_actifs and get_rappels_par_categorie_etablissement (the latter is a filtered version of the former). Nonetheless, descriptions clarify the differences.

Naming Consistency4/5

The naming convention is almost entirely 'get_<noun>', which is consistent. The exception is 'compare_solutions_haccp' which uses 'compare_' instead of 'get_', breaking the pattern. This is a minor inconsistency.

Tool Count5/5

19 tools cover a comprehensive range of HACCP-related topics for French catering. Each tool addresses a specific need without excessive overlap, and the number is well within the ideal 3-15 range, earning a high score.

Completeness5/5

The tool set covers all major aspects of HACCP compliance in France: training, temperatures, cleaning plans, recalls, inspection risk, sanctions, allergens, DLC rules, etc. There are no obvious gaps for an informational/retrieval tool of this nature.