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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| queryA | Execute SQL query on ANSES Ciqual French food composition database. IMPORTANT: Get ALL nutrients in ONE query! Don't make multiple queries for the same food. EXAMPLE - Get complete nutrition for a food: SELECT f.alim_nom_eng, n.const_nom_eng, 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 = 23000; -- Returns ALL 60+ nutrients in one query! SCHEMA: • foods: 3,185+ foods with French/English names
• nutrients: ~60+ nutrients with units
• composition: nutritional values per 100g
• foods_fts: full-text search for fuzzy matching
COMMON QUERIES:
KEY NUTRIENT CODES: Energy: 327 (kJ), 328 (kcal) Macros: 25000 (protein g), 31000 (carbs g), 40000 (fat g), 34100 (fiber g), 32000 (sugars g) Minerals: 10110 (sodium mg), 10200 (calcium mg), 10260 (iron mg), 10190 (potassium mg) Vitamins: 55400 (vit C mg), 56400 (vit D µg), 51330 (vit B12 µg), 56310 (vit E mg) The database is read-only. Use SELECT queries only. |
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 named 'query', there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as executing SQL queries on the ANSES Ciqual database, making it straightforward for an agent to select.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'query' follows a simple, clear verb pattern that aligns with its function, and there are no other tools to cause inconsistency.
The server has only one tool, which is too few for its apparent scope of providing access to a complex food composition database with multiple tables and query types. A single SQL query tool places excessive burden on the agent to construct correct queries, lacking specialized tools for common operations like searching foods or retrieving nutrients.
The tool surface is severely incomplete for the domain. While the 'query' tool allows access to all data, it lacks dedicated tools for key operations such as food search, nutrient lookup, or retrieving specific food compositions, which are essential for a food database. This forces agents to handle complex SQL, increasing the risk of errors and inefficiencies.