Schema | Calorie Tracker MCP

Calorie Tracker MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
log_mealC	Log a meal using caller-supplied estimates and an idempotency key.
get_mealA	Get one meal by its server-generated id.
list_mealsC	List meals using bounded profile-local filters.
update_mealC	Update selected meal fields after checking its expected revision.
delete_mealA	Soft-delete a meal after checking its expected revision.
restore_mealB	Restore a soft-deleted meal after checking its expected revision.
get_meal_historyA	Get immutable revision history for one meal.
set_goalsB	Set effective-dated daily calorie and protein goals.
get_goalsA	Get the goals applicable on a profile-local date.
get_summaryB	Summarize meals for one date or an inclusive date range.
export_mealsA	Export a bounded meal page as JSON or CSV, inline or to a local path.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Yani3rt/Calorie_tracker_mcp_cli'

If you have feedback or need assistance with the MCP directory API, please join our Discord server