YAZIO MCP

Overview Schema Source Related Servers Discussions Admin

Add consumed item

add_consumed_item

Idempotent

Add a food item to your YAZIO nutrition diary for a specific date and meal time. Preview the entry, check for duplicates, and get the updated diary after saving.

Instructions

Shows a preview, checks for duplicates, writes idempotently, and rereads the diary. dry_run defaults to true.

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": {
      "client_request_id": "<client_request_id>",
      "product_id": "<product_id>",
      "date": "<date>",
      "daytime": "<daytime>",
      "amount": "<amount>"
    },
    "name": "add_consumed_item"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes
`amount`	Yes
`daytime`	Yes
`dry_run`	No
`serving`	No
`product_id`	Yes
`serving_quantity`	No
`client_request_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

B3.3/5.0

Behavior4/5

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

The description discloses side effects: preview, duplicate checking, idempotent write, and diary reread. This goes beyond annotations which only indicate readOnly=false, idempotent=true, and destructive=false. No contradictions exist.

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 a single sentence, efficient, and front-loaded with the most important behavior. Every word adds value, and there is no wasted text.

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

Completeness3/5

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

For an 8-parameter tool with an output schema, the description covers core behavior but lacks parameter semantics and usage context. The presence of annotations and output schema helps, but the description alone is insufficient for correctly invoking the tool with all parameters.

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?

The schema has no descriptions, and the description only mentions the dry_run default. It doesn't explain client_request_id, serving, serving_quantity, or how duplicate detection works. This fails to compensate for the 0% schema coverage.

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

Purpose4/5

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

The tool name and title clearly indicate adding a consumed item. The description adds specific behavioral details (preview, duplicate check, idempotent write, diary reread) that distinguish it from sibling tools like update_consumed_item or add_meal_batch, though it doesn't explicitly state the primary 'add' function.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It implies a single-item add with dry-run capability but doesn't mention batch tools or exclusions. It also doesn't describe prerequisites such as whether the product must already exist.

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

Deploy Server