YAZIO MCP

by tomastaker

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Remove consumed item

remove_consumed_item

DestructiveIdempotent

Remove a specific food entry from your YAZIO nutrition diary. Confirm with a token to finalize the deletion.

Instructions

Removes only the specified diary item ID after MRTR confirmation. Fallback: a dry run issues a one-time confirmation_token with a TTL.

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>",
      "item_id": "<item_id>",
      "date": "<date>"
    },
    "name": "remove_consumed_item"
  }
}

Input Schema

Name	Required	Description	Default
`date`	Yes
`dry_run`	No
`item_id`	Yes
`client_request_id`	Yes
`confirmation_token`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 7, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already indicate destructive and idempotent behavior, but the description adds crucial behavioral details: the requirement of MRTR confirmation, the dry-run fallback that issues a one-time confirmation_token, and the TTL. This significantly enriches understanding beyond the annotations.

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 the core action ('Removes only the specified diary item ID') and then the fallback detail. Every word earns its place with no redundancy.

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

Completeness4/5

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

The description covers the core removal action and the confirmation flow, which is sufficient given the output schema exists and annotations cover idempotency/destructiveness. However, the acronym 'MRTR' is unexplained, and the description does not mention any error or prerequisite conditions beyond confirmation, leaving some gaps for a complex deletion flow.

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 0%, so the description must compensate. It explains item_id ('the specified diary item ID') and dry_run/confirmation_token ('a dry run issues a one-time confirmation_token with a TTL'). However, date and client_request_id remain unexplained, leaving some parameters without added meaning.

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 verb 'Removes' with a specific resource ('the specified diary item ID'), distinguishing it from siblings that add or update consumed items. The phrase 'only the specified' reinforces its single-item scope.

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

Usage Guidelines4/5

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

The description implies this tool is for removing exactly one diary item (not batch operations) and requires MRTR confirmation, which gives usage context. However, it does not explicitly name alternative tools like update_consumed_item, though no other sibling directly removes items, so the intended use is fairly clear.

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

Deploy Server