Skip to main content
Glama

Frigolog HACCP — French Food Safety Compliance

get_score_alimconfiance

Retourne le fonctionnement complet du score Alim'confiance, dispositif officiel de publication des résultats d'inspection sanitaire DDPP en France depuis avril 2017 (alim-confiance.gouv.fr). Détaille les 4 niveaux de notation (très satisfaisant, satisfaisant, à améliorer, à corriger de manière urgente), les 6 critères d'évaluation, la fréquence des inspections (3 à 7 ans en moyenne), et les actions concrètes pour améliorer son score lors d'un contrôle officiel. Pour récupérer le score d'un établissement précis, utilisez get_alimconfiance_etablissement.

[EN] Explains how France's official Alim'confiance sanitary-inspection scoring works (4 levels, 6 criteria, inspection frequency, how to improve). For one establishment's score, use get_alimconfiance_etablissement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It explains what the tool returns (informational content) but does not explicitly state that it is read-only or has no side effects. However, as an informational tool, the description is mostly 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 fairly detailed but includes an English translation that repeats information. It is front-loaded with key purpose and usage guidance. Could be slightly more concise, but still effective.

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 no output schema and no parameters, the description fully covers what the tool returns: the 4 score levels, 6 criteria, inspection frequency, and improvement actions. It is complete for an informational tool.

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 input schema has zero parameters, so baseline is 4. The description does not need to add parameter info; it correctly focuses on the tool's purpose and output.

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 the tool returns the complete functioning of Alim'confiance scoring, detailing levels, criteria, inspection frequency, and improvement actions. It explicitly distinguishes from the sibling tool get_alimconfiance_etablissement by noting that the latter retrieves an establishment's specific score.

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?

The description provides explicit guidance: use this tool to understand the scoring system, and for a specific establishment's score, use get_alimconfiance_etablissement. This clearly indicates when to use this tool versus the alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

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.