Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

by io.github.naimterrache-a11y

get_calendrier_obligations

Retourne le calendrier des obligations réglementaires HACCP à venir pour un établissement, basé sur les dates de ses dernières actions : date de dernière formation HACCP (obligation de recyclage tous les X ans), date de dernier contrôle DDPP (fréquence moyenne des inspections par type et département), date de dernier audit interne, date de dernier changement de Plan de Maîtrise Sanitaire. Pour chaque obligation, retourne la date prévisionnelle, le niveau d'urgence (vert/orange/rouge), et l'action recommandée. Conçu pour l'automatisation : un agent IA peut appeler ce tool chaque semaine et alerter le gérant des échéances à venir.

[EN] Returns the calendar of upcoming HACCP regulatory obligations for an establishment, based on dates of last actions: last HACCP training (renewal obligation), last DDPP inspection (average inspection frequency by type and department), last internal audit, last PMS update. For each obligation, returns the estimated due date, urgency level (green/orange/red), and recommended action. Designed for automation. Required 'type_etablissement'; optional last-action dates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
departementNoCode département français (ex: '75', '2A', '971'). Optionnel, informatif.
dernier_maj_pmsNoDate ISO (YYYY-MM-DD) de la dernière mise à jour du Plan de Maîtrise Sanitaire. Optionnel.
type_etablissementYesType d'établissement (pour la fréquence d'inspection DDPP). Valeurs : 'restaurant', 'boulangerie', 'boucherie', 'fromagerie', 'poissonnerie', 'traiteur', 'glacier', 'pizzeria', 'patisserie', 'collectivite'.
dernier_audit_interneNoDate ISO (YYYY-MM-DD) du dernier audit interne du PMS. Optionnel.
dernier_controle_ddppNoDate ISO (YYYY-MM-DD) du dernier contrôle DDPP. Optionnel.
derniere_formation_haccpNoDate ISO (YYYY-MM-DD) de la dernière formation/recyclage hygiène HACCP. Optionnel.

TDQS

A4.3/5.0
Behavior3/5

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

Describes the logic (based on last-action dates) and outputs (due date, urgency, action). No annotations provided, so description carries full burden—does not explicitly state it's read-only or discuss authorization/rate limits; but does not hide destructive behavior.

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-language description is front-loaded with key action verb ('Retourne'), short sentences, no superfluous information. Every sentence adds value.

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 6 parameters and no output schema, the description adequately explains the expected output (urgency, due date, action) and the tool's automation purpose. Minor gap: could mention if it handles missing optional dates gracefully.

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

Parameters5/5

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

Schema coverage is 100%, and description adds business context (e.g., 'recyclage tous les X ans', 'fréquence moyenne des inspections') beyond the schema descriptions. Explicitly highlights required parameter.

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 it returns the calendar of upcoming HACCP obligations for an establishment, using specific dates. It distinguishes from sibling tools like 'get_score_alimconfiance' or 'get_risque_inspection' by focusing on a computed calendar of obligations.

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?

Explicitly designed for automation (weekly call and alert), and mentions required parameter. No explicit when-not-to-use or exclusion of siblings, but the use case is clear.

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