Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

by io.github.naimterrache-a11y

get_haccp_temperatures

Renvoie les températures réglementaires françaises de conservation, refroidissement et service des denrées alimentaires par catégorie de produit, conformément à l'arrêté du 21 décembre 2009, au règlement (CE) n° 852/2004 et au règlement (CE) n° 853/2004 (denrées d'origine animale). Couvre viandes, poisson, produits laitiers, œufs, fruits et légumes, plats cuisinés, pâtisseries, surgelés, glaces, températures de service chaud et de refroidissement rapide.

[EN] Returns French regulatory food temperatures (storage, cooling, serving) by product category, per the arrêté of 21 Dec 2009 and Regulations (EC) 852/2004 & 853/2004. Optional 'categorie' filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categorieNoFiltre optionnel par catégorie. Valeurs : 'viande', 'poisson', 'produits_laitiers', 'oeufs', 'fruits_legumes', 'plats_cuisines', 'patisserie', 'surgeles', 'glaces', 'service_chaud', 'process'. 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?

With no annotations, the description carries the burden. It describes a read-only lookup with no side effects, but does not explicitly state idempotency or non-destructiveness. It is adequate but not fully explicit.

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 front-loaded with key information and is concise despite being bilingual. No unnecessary sentences, though bilingualism adds length.

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 the simple lookup nature and full schema coverage, the description is sufficiently complete. It states the regulatory basis and optional filter, though it does not describe the return structure (no output schema exists).

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%, and the description only adds the optional filter mention. The schema already fully documents the parameter and its values; the description adds no new semantic meaning.

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 explicitly states it returns French regulatory food temperatures by product category, citing specific regulations. It distinguishes from sibling tools like get_temperatures_cuisson (cooking temperatures) and get_seuils_microbiologiques, making its unique purpose clear.

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 mentions the optional 'categorie' filter but does not provide explicit guidance on when to use this tool versus siblings. The context is implied but lacks direct when/when-not instructions or alternatives.

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