Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

by io.github.naimterrache-a11y

get_regles_dlc

Renvoie les règles de DLC (Date Limite de Consommation) pour les préparations maison en restauration et métiers de bouche en France, conformément au Guide des Bonnes Pratiques d'Hygiène en Restauration de la DGAL. Couvre viandes cuites/crues, salades composées, sandwiches, pâtisseries à la crème, sauces (émulsionnées et cuites), soupes, plats cuisinés, sous-vide cuisson basse température, produits décongelés, produits entamés. Pour chaque préparation : DLC en jours, température de conservation requise, source réglementaire.

[EN] Returns use-by-date (DLC) rules for in-house preparations in French restaurants and food trades, per the DGAL good-hygiene-practice guide. Optional 'type_preparation' keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
type_preparationNoFiltre optionnel par type de préparation. Recherche par mot-clé dans le nom (ex: 'viande', 'salade', 'sauce', 'pâtisserie', 'soupe', 'sous-vide'). Si absent, renvoie toutes les catégories.

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided. The description details what the tool returns (DLC in days, temperature, source) and covers many categories, but does not disclose any limitations, authorization needs, or data freshness.

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 well-structured with French then English, front-loaded with purpose. It is slightly verbose but each 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?

Given no output schema and no annotations, the description is fairly complete for a reference tool, covering scope, parameter usage, and examples. Could specify return format details but acceptable.

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 coverage is 100% and already describes the parameter well. The description adds examples but does not significantly enhance meaning 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 clearly states the tool returns DLC rules for in-house preparations in French restaurants, listing specific preparation types. It distinguishes from sibling tools which cover HACCP, inspections, scores, etc.

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 clarifies the tool is for DLC rules in French restaurants and mentions an optional filter, but it does not explicitly state when to use it over siblings or when not to use it.

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