Skip to main content
Glama
davidmosiah

Wellness Nourish

Update intake

nourish_update_intake
Idempotent

Update a logged food intake entry by ID. Modify quantity, meal type, or grams, and automatically rescale nutrients to maintain summary consistency.

Instructions

Update a local intake entry by id. Quantity or grams_estimate changes rescale nutrients to keep summaries consistent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
meal_typeNo
quantityNo
unitNo
grams_estimateNo
timestampNo
notesNo
tagsNo
response_formatNojson
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate idempotency and non-destructiveness. The description adds beyond annotations by revealing that quantity or grams_estimate changes trigger nutrient rescaling, which is critical behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at two sentences, front-loading the core purpose and adding one critical detail without extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite annotations, the description lacks parameter guidance, expected return values, error handling, or prerequisites. Given the tool's 9 parameters and no output schema, this is insufficient for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description only explains id, quantity, and grams_estimate. It omits meaning for meal_type, unit, timestamp, notes, tags, and response_format, leaving significant gaps for the agent.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool updates a local intake entry by id and specifies a key behavioral detail about rescaling nutrients on quantity or grams_estimate changes, distinguishing it from related tools like delete or log.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for updates but provides no explicit guidance on when to choose this tool over alternatives like nourish_log_intake or nourish_delete_intake, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/davidmosiah/wellness-nourish'

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