Skip to main content
Glama
mijneetmeter-mcp

mijneetmeter-mcp

by jhofstede

add_food

Add a food item to a Dutch food diary for a specific date and meal after finding the product with search_food.

Instructions

Add a food item to the diary. Call search_food first to get product_id, product_type and synonym_id. The result lists the units the product supports (units_available) and which one was used.

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": {
      "date": "<date>",
      "meal": "<meal>",
      "product_name": "<product_name>",
      "product_id": "<product_id>",
      "product_type": "<product_type>"
    },
    "name": "add_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate in DD-MM-YYYY format
mealYesMeal moment: ontbijt/breakfast, lunch, avondeten/dinner, tussendoor/snack
amountNoQuantity, in the chosen unit (default 1)
product_idYesId (UUID) from search_food
synonym_idNoSynonymId from search_food (omit if null)
unit_indexNoWhich unit of the product to use, 1-based (default 1 = first unit)
product_nameYesProductName from search_food
product_typeYesType from search_food (1/2/4)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so the safety profile is covered. The description adds value beyond that by disclosing a cross-tool dependency (search_food must run first) and a return detail (units_available plus which unit was used), which the annotations cannot convey.

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?

Three short sentences, front-loaded with the action, then the prerequisite, then the return behavior. No redundant restatement of the tool name and no filler.

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?

For an 8-parameter mutation tool with no output schema, the definition covers the action, the required upstream call, and part of the response shape, which is enough to invoke it correctly. It is slightly thin on what happens on failure or duplicate entries, but nothing essential is missing.

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 every parameter is already documented in the schema, establishing a baseline of 3. The description adds the useful provenance note that product_id, product_type and synonym_id come from search_food, and hints that unit_index maps into units_available, but it adds no format or default detail beyond the schema.

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 description names a specific verb and resource ("Add a food item to the diary"), which unambiguously separates it from search_food, delete_food, and the get_diary readers. It stops short of an explicit contrast statement against siblings, but the action is unmistakable.

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?

It gives a concrete prerequisite workflow: call search_food first to obtain product_id, product_type and synonym_id. That is clear when-to-use context, though it offers no when-not guidance (e.g., adding to favorites versus the diary) and no error/precondition handling advice.

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