ANSES Ciqual MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Execute SQL query on ANSES Ciqual French food composition database. ā ļø EFFICIENCY: Follow this 2-step workflow to minimize queries! STEP 1 - SEARCH (one query): SELECT alim_code, alim_nom_fr FROM foods_fts WHERE foods_fts MATCH 'steak OR boeuf'; Note: FTS uses OR between words. For "steak sauce poivre", search "steak" first. STEP 2 - GET ALL NUTRIENTS (one query with JOIN): SELECT f.alim_nom_fr, n.const_nom_fr, c.teneur, n.unit FROM foods f JOIN composition c ON f.alim_code = c.alim_code JOIN nutrients n ON c.const_code = n.const_code WHERE f.alim_code = ; š STOP after finding a matching food! Don't keep searching with different terms. COMPOUND DISHES (steak + sauce):
QUICK CALORIE LOOKUP (const_code 328 = kcal/100g): SELECT f.alim_nom_fr, c.teneur as kcal_100g FROM foods f JOIN composition c ON f.alim_code = c.alim_code WHERE f.alim_code = AND c.const_code = 328; KEY NUTRIENT CODES: Energy: 328 (kcal), 327 (kJ) Macros: 25000 (protein), 31000 (carbs), 40000 (fat), 34100 (fiber), 32000 (sugars) Minerals: 10110 (sodium), 10200 (calcium), 10260 (iron), 10190 (potassium), 10120 (magnesium) Vitamins: 55100 (vit C), 52100 (vit D), 56600 (vit B12), 53100 (vit E), 56700 (folates) SCHEMA:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly stated as executing SQL queries on the food composition database.
The sole tool is named 'query', a simple and unambiguous name. While there is no pattern to compare, the lack of multiple tools means there is no inconsistency in naming conventions.
The server exposes only one tool, which feels thin for the broad scope of a food composition database. Although the tool is powerful and can execute arbitrary SQL, a single tool places a heavy burden on the agent and lacks dedicated conveniences.
The generic SQL query tool can access all tables, perform joins, filters, and full-text searches, covering every potential query needed. The provided schema, examples, and nutrient codes ensure agents have enough information to retrieve any data, making the surface functionally complete.