Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

by io.github.naimterrache-a11y

get_sanctions_ddpp

Retourne les sanctions et risques d'inspection applicables lors d'un contrôle DDPP en restauration et métiers de bouche en France : 4 niveaux (observation, mise en demeure, procès-verbal, fermeture administrative), seuils déclencheurs, délais de mise en conformité, montants d'amende (de 1 500 € à 75 000 €), risques d'emprisonnement et voies de recours. Base légale : Code rural et de la pêche maritime articles L.231-1 à L.237-3, règlement CE 852/2004, arrêté du 21 décembre 2009.

[EN] Returns DDPP inspection sanction levels in France (observation, formal notice, report, administrative closure): triggers, deadlines, fines (€1,500–€75,000), legal basis (Code rural). Optional 'gravite'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
graviteNoFiltre optionnel par niveau de gravité. Valeurs : 'mineure', 'majeure', 'critique', 'tous'. Si absent ou 'tous', renvoie l'ensemble des niveaux de sanction.

TDQS

A3.9/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that the tool returns four sanction levels, thresholds, deadlines, fines, and legal basis. It also notes the optional 'gravite' filter. This is comprehensive for a read-only query tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is dense with information but includes bilingual repetition (French and English). It front-loads key details, but the structure could be tighter to avoid redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, description explains return values (sanction levels, fines, etc.) but does not specify output format (e.g., array of objects, structure). Legal basis is included, but more detail on how the information is organized would improve completeness.

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?

Schema coverage is 100% with one parameter 'gravite' described as optional filter. Description adds meaning by explaining the default behavior (if absent or 'tous', returns all levels) and listing possible values, going beyond the schema's description.

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?

Description clearly states it returns sanctions and risks for DDPP inspections in French food businesses, listing levels, triggers, fines, and legal basis. It distinguishes from sibling tools focused on other aspects (e.g., HACCP, corrective actions).

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?

Description implies use when sanction details are needed, but lacks explicit guidance on when to use this tool versus alternatives like get_risque_inspection or get_documents_controle_ddpp. No when-not or exclusion criteria.

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