Skip to main content
Glama
Nutrition MCP
by ronkommoji

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NUTRITION_MCP_HOMENoOverride the storage location. Default is ~/.nutrition-mcp~/.nutrition-mcp

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

CapabilityDetails
tools
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
setup_profileB

Create the nutrition tracking profile used for daily goals and timezone-aware logging.

update_profileC

Update profile fields such as calorie goal, protein goal, weight, goal type, or timezone.

log_foodA

Store a confirmed food entry. The agent supplies calories and protein (estimated with its own knowledge or web search). Requires userConfirmed: true.

undo_last_logA

Remove the most recent food log entry, optionally constrained to a specific date.

get_daily_statusA

Return calories, protein, remaining goals, and entries for a day.

get_weekly_summaryA

Return weekly calorie and protein averages, best day, and tracked-day count.

search_food_historyB

Search previous logged meals by raw text or parsed food item names.

export_logsC

Export profile and food logs as JSON or CSV text.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
user_profileCurrent nutrition tracking profile.
daily_summaryCurrent day calorie and protein totals.

TDQS

A3.5/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target clearly different actions and resources (logging, daily status, weekly summary, search, export, undo). The only mild overlap is setup_profile vs. update_profile, though the create-vs-modify distinction is spelled out in the descriptions.

Naming Consistency5/5

All eight names follow a consistent snake_case verb_noun pattern (setup_profile, log_food, get_daily_status, export_logs, etc.). Verb choices are predictable even though they vary by action.

Tool Count5/5

Eight tools is well within the ideal 3-15 range and each maps to a distinct part of the nutrition-tracking workflow. No tool feels redundant or missing for the core loop.

Completeness4/5

The surface covers profile setup/update, food logging, daily/weekly reads, history search, export, and single-step undo. Minor gaps exist: no way to edit or delete an arbitrary log entry (only undo the last), and no explicit get_profile read despite update/setup coverage.

Maintenance

ActivityInactive
ResponsivenessNo recent community issues