Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

by io.github.naimterrache-a11y

get_rappels_produits_actifs

Retourne les rappels et retraits de lots de produits alimentaires actifs en France en temps réel depuis RappelConso (DGCCRF). Source officielle : data.economie.gouv.fr (dataset rappelconso-v2-gtin-trie). Utilisez ce tool pour vérifier la sécurité alimentaire d'un produit avant service, savoir si une référence fait l'objet d'un rappel ou retrait de lots en cours, ou consulter les dernières alertes sanitaires officielles publiées par la Direction Générale de la Concurrence, de la Consommation et de la Répression des fraudes.

[EN] Returns active French food-product recalls in real time from RappelConso (DGCCRF open data). Filters: 'categorie', 'limit', 'date_depuis'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNombre maximum de rappels à retourner (défaut 10, maximum 50). Les plus récents en premier.
categorieNoFiltre optionnel par catégorie d'aliment. Valeurs : 'viande', 'poisson', 'produits_laitiers', 'boulangerie', 'epicerie', 'tous'. Si absent ou 'tous', renvoie toutes les catégories alimentaires.
date_depuisNoDate de publication minimale des rappels au format YYYY-MM-DD. Si absent, renvoie les plus récents sans limite de date.

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions real-time updates and the official source, but does not disclose read-only nature, authentication requirements, result structure, or pagination behavior.

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 bilingual, which adds length but is contextually valuable. It front-loads the purpose and is structured well, though it could be slightly more concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema, and the description does not describe the fields or structure of the returned recall data, leaving the agent uncertain about what information it will receive.

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 the baseline is 3. The tool description adds no additional meaning beyond listing the filters already documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states that the tool returns active French food product recalls from RappelConso, using specific verbs and resources. However, it does not explicitly distinguish this tool from siblings like 'get_rappels_par_categorie_etablissement'.

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 lists use cases like checking product safety before service and viewing official alerts, but it does not provide guidance on when not to use this tool or mention alternatives among siblings.

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

All Frigolog HACCP — French Food Safety Compliance 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.

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.

Resources