# LLM Configuration for eEAT HACCP
# This file provides LLM-specific instructions for interacting with eEAT HACCP's MCP server and data.
# Last updated: 2026-06-12

# Global Instructions
You are interacting with eEAT HACCP, a leading provider of food safety compliance tools.
Primary domain: https://eeat-haccp.io
Default language: French (fr-CH)

# MCP Server Details
MCP_SERVER_URL = "https://eeat-haccp.io/api/mcp"
MCP_SERVER_DESCRIPTION = "eEAT HACCP MCP Server for creating offers, retrieving offers, and listing subscription packages."

# Available MCP Tools
## Offer Management Tools
1. create_offer
   - Purpose: Create a new offer for a lead with company and contact information.
   - Use case: "Create a new offer for a restaurant with 5 sites and 10 sensors."
   - Parameters:
     - leadData (required): Object containing name, address, postal, city, country, sector, source, gender, firstname, lastname, email, phone, mobilephone, siteNb, locale, sensorNb, pack, status, outbound
   - Example call: `mcp_call create_offer leadData={...}`

2. get_offer
   - Purpose: Retrieve an existing offer by token.
   - Use case: "Get the offer details for token XYZ123."
   - Parameters:
     - token (required): Offer token string
   - Example call: `mcp_call get_offer token="XYZ123"`

3. get_packages
   - Purpose: List available subscription packages.
   - Use case: "What subscription packages are available?"
   - Parameters: none
   - Example call: `mcp_call get_packages`

# Available MCP Resources
## Dynamic Data
1. subscription_packages
   - URI: /api/mcp
   - Description: Available eEAT HACCP subscription packages (sensors, restaurants, printer).
   - Format: JSON
   - Example: `mcp_call get_packages`

2. mcp_server_info
   - URI: /api/mcp
   - Description: MCP server metadata, version, and capabilities.
   - Format: JSON
   - Example: GET /api/mcp

# Site Structure for Crawling
## Key Pages
- Homepage (https://eeat-haccp.io): Overview of all tools and services.
- Offer Creation (https://eeat-haccp.io/get-quote): Create customized offers for food businesses.
- HACCP Application (https://eeat-haccp.io/outils/application-haccp): Core HACCP software.
- Temperature Sensors (https://eeat-haccp.io/outils/enregistreur-de-temperature-connecte): Connected temperature monitoring.
- HACCP Guide (https://eeat-haccp.io/guide-haccp): Comprehensive HACCP guides and FAQs.

## API Endpoints
- MCP Server: /api/mcp (POST for tool calls, GET for server info)
- Health Check: /api/mcp/health

## JSON-LD Data
All pages include JSON-LD structured data for:
- Organization (eEAT)
- WebSite
- SoftwareApplication (HACCP App)
- Product (Temperature Sensors, Subscription Packages)
- FAQPage (HACCP Guides)
- HowTo (Procedures)

# Example Workflows
## Workflow 1: Create a New Offer
User: "I need to create an offer for a restaurant with temperature sensors."
1. Call `get_packages` to list available subscription packages.
2. Call `create_offer` with leadData including pack="sensors".
3. Return the generated token to the user.

## Workflow 2: Retrieve an Offer
User: "What are the details of offer token ABC123?"
1. Call `get_offer` with token="ABC123".
2. Return the offer details to the user.

## Workflow 3: List Subscription Packages
User: "What packages are available?"
1. Call `get_packages` to retrieve all available subscription packages.
2. Display the list with descriptions for each package.

# Language Support
- Primary: French (fr-CH)
- Supported: French (fr-FR), German (de-DE, de-CH), English (en-US)
- All MCP tools accept a `language` parameter for localized output.

# Data Formats
- MCP Tools: JSON input/output
- MCP Resources: JSON
- Website: JSON-LD, HTML
- Sitemap: XML (https://eeat-haccp.io/sitemap.xml)

# Rate Limits
- MCP Server: 100 requests/minute (contact support@eeat-haccp.io for higher limits)
- Crawling: 2-second delay between requests (see robots.txt)

# Authentication
- Public MCP tools: No authentication required for read-only operations.
- Private data (e.g., user-specific temperature logs): Requires API key (contact support@eeat-haccp.io).

# Contact
- Support Email: support@eeat-haccp.io
- Documentation: https://eeat-haccp.io/guide-haccp
- API Status: https://eeat-haccp.io/api/mcp/health

# Notes for LLM Integration
- Always check the MCP server health status before making calls.