Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

by io.github.naimterrache-a11y

get_temperatures_cuisson

Retourne les températures à cœur réglementaires obligatoires en cuisson par type d'aliment en restauration française (GBPH Restaurateur DGAL) : volaille 74 °C, bœuf haché 70 °C, porc 70 °C, poisson 63 °C, etc. Inclut le refroidissement rapide (de +63 °C à +10 °C en moins de 2 heures), la remise en température à +63 °C minimum et les recommandations de sécurité spécifiques aux populations sensibles (enfants, femmes enceintes, immunodéprimés). Distinct des températures de conservation disponibles via get_haccp_temperatures.

[EN] Returns mandatory core cooking temperatures by food type in French catering (poultry 74°C, minced beef 70°C, fish 63°C…) plus rapid cooling and reheating rules. Optional 'type_aliment'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
type_alimentNoFiltre optionnel par type d'aliment ou de procédé. Recherche par mot-clé dans l'identifiant ou l'intitulé (ex: 'volaille', 'boeuf', 'poisson', 'refroidissement', 'remise'). Si absent, renvoie tous les aliments et procédés.

TDQS

A4.5/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 for behavioral disclosure. It discloses that the tool includes cooling, reheating rules, and safety recommendations for sensitive populations. It also mentions the optional filter, providing clear behavioral context beyond simple retrieval.

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?

Description is front-loaded with the main purpose and includes both French and English versions, which is helpful for bilingual users. It is reasonably concise, though the English translation adds some redundancy. Overall efficient.

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, the description explains what the tool returns (core cooking temperatures, cooling and reheating rules). However, it does not specify the exact return format or data structure, which would be helpful for agents. Still, for a simple one-parameter tool, it is largely complete.

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 has 100% description coverage, so baseline is 3. The description adds minimal value beyond the schema, only restating that type_aliment is optional. The schema already explains the filter behavior well.

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 that the tool returns mandatory core cooking temperatures by food type in French catering, providing specific examples (poultry 74°C, minced beef 70°C, etc.). It also distinguishes itself from the sibling tool get_haccp_temperatures, which covers conservation temperatures.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states that the tool is distinct from conservation temperature tool and names the alternative (get_haccp_temperatures). This provides clear when-to-use and when-not-to-use guidance.

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