Skip to main content
Glama
Sign In
fliptheweb

yazio-mcp

by fliptheweb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_user_consumed_item

Log a consumed food item to a user's Yazio diary with date, meal type, and amount; include time to preserve entry timing.

Instructions

Add a food item to user consumption log. Pass date with time ("YYYY-MM-DD HH:mm:ss") to keep the time of the entry; date only (YYYY-MM-DD) logs it at 00:00.

Input Schema

NameRequiredDescriptionDefault
dateYesDate and time when the food was consumed in "YYYY-MM-DD HH:mm:ss" format (e.g., "2025-12-18 12:30:00"), or date only in YYYY-MM-DD format
amountYesAmount of the product consumed in base units (g or ml)
daytimeYesType of meal (breakfast, lunch, dinner, snack)
servingNoServing type (e.g. portion, fruit, glass, cup, slice, piece, bar, gram, bottle, can, etc.)
product_idYesProduct UUID v1/v4 (e.g. 4ceff6e9-78ce-441b-964a-22e81c1dee92)
serving_quantityNoQuantity of servings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.0.15
    • addedInput schema / properties / date / anyOf
      Added value: +[
+  {
+    "description": "Date in YYYY-MM-DD format",
+    "format": "date",
+    "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
+    "type": "string"
+  },
+  {
+    "pattern": "^\\d{4}-\\d{2}-\\d{2} \\d{2}:\\d{2}:\\d{2}$",
+    "type": "string"
+  }
+]
    • changedInput schema / properties / date / description
      Previous value: -"Date when the food was consumed"New value: +"Date and time when the food was consumed in \"YYYY-MM-DD HH:mm:ss\" format (e.g., \"2025-12-18 12:30:00\"), or date only in YYYY-MM-DD format"
    • removedInput schema / properties / date / format
      Removed value: -"date"
    • removedInput schema / properties / date / pattern
      Removed value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
    • removedInput schema / properties / date / type
      Removed value: -"string"
  2. First observedv0.0.12

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=false, so the mutation and duplicate-on-retry traits are covered structurally. The description adds one genuinely useful behavioral detail: date-only input is normalized to 00:00, which affects stored data. It does not mention auth/ownership requirements or what the response contains.

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?

Two sentences, front-loaded with what the tool does, then the one behavioral nuance that matters. No repetition or filler.

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?

Adequate for invocation: annotations carry the safety profile and the schema carries parameter meaning. However, for a write tool with no output schema, it says nothing about the result of the call (new entry id, updated totals) or how serving vs amount interact, leaving real gaps.

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

Parameters3/5

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

Schema coverage is 100%, so all six parameters are documented in the schema; baseline is 3. The description only reinforces the date parameter's dual format and its midnight normalization, adding nothing about how amount relates to serving/serving_quantity, which is the main semantic ambiguity left.

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?

States a specific verb and resource: 'Add a food item to user consumption log.' An agent can distinguish this from get_user_consumed_items and remove_user_consumed_item by the write verb, though no sibling is named explicitly.

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?

Usage guidance is limited to date-format behavior (with time vs date-only, and the resulting 00:00 log time). There is no statement of when to use this versus remove_user_consumed_item, no prerequisite that product_id comes from search_products, and no note about the relationship between amount and serving_quantity.

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

Deploy Server

Other Tools