get_client_preferences
The client's own stated constraints — diet type, food allergies, cuisines, meals per day, cooking level, which days they can train, home vs gym, what equipment they actually have, preferred time and session length, plus free-text notes. These are hard constraints, not suggestions: a diet plan that violates dietType, foodAllergies or mealsPerDay is rejected outright by the server, and a workout plan built for equipment they don't own is unusable. Call this BEFORE create_workout_plan/create_diet_plan on every run, including weekly adjustments — clients change these between runs, and the previous plan does not tell you what they say today. Returns null if they have not set any.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"clientId": "<clientId>"
},
"name": "get_client_preferences"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| clientId | Yes |