Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

by io.github.naimterrache-a11y

get_formation_haccp_obligatoire

Retourne les obligations légales de formation hygiène alimentaire HACCP en restauration commerciale en France : qui doit obligatoirement se former (restauration traditionnelle, rapide, traiteur, food trucks), qui est exempté (3 ans d'expérience ou diplômés), contenu obligatoire de la formation, durée pratique (14 heures), coût moyen, organismes certifiés Qualiopi, validité et sanction (jusqu'à 1 500 €) en cas d'absence de formation lors d'un contrôle DDPP. Base légale : article L.233-4 du Code rural, arrêté du 5 octobre 2011 modifié 12 février 2024.

[EN] Returns the mandatory food-hygiene (HACCP) training rules for French commercial catering: who must train, exemptions, content, duration, cost, penalties. Legal basis: Code rural L.233-4, arrêté of 12 Feb 2024. Optional 'type_etablissement' (informational).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
type_etablissementNoFiltre optionnel par type d'établissement (à titre informatif — l'obligation de formation est la même pour tous les types de restauration commerciale). Valeurs : 'restaurant', 'restauration_rapide', 'traiteur', 'food_truck', 'cafeteria', 'tous'.

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden and discloses the tool's behavior well: it returns static regulatory information, lists what it covers (who, exemptions, content, etc.), and notes the parameter is merely informational. It does not reveal potential limitations like data freshness, but for an informational tool this is adequate.

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 somewhat lengthy with bilingual repetition, but it is well-structured with clear sections covering different aspects. The front-loaded French summary is efficient, and every sentence adds information. Could be slightly more concise, but it earns its place.

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 the tool returns static legal information with one optional parameter and no output schema, the description is comprehensive. It covers all key points: who must train, exemptions, content, duration, cost, penalties, and legal basis. No additional information seems necessary.

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?

The schema covers the only parameter with full description (100% coverage). The description adds value by stating that the parameter is 'informational' and that the obligation is the same for all types, clarifying that the result does not change based on the parameter. This extra context helps the agent understand the parameter's limited role.

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 the tool returns mandatory HACCP training rules for French commercial catering. It specifies the resource (obligations légales) and the verb (Retourne), and distinguishes from sibling tools which cover different aspects like corrective actions or checklists.

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 implies usage for general information on training obligations but does not explicitly state when to use this tool versus siblings. There is no guidance on alternatives or exclusions, but the context prevents it from being misleading.

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