Skip to main content
Glama
mijneetmeter-mcp

mijneetmeter-mcp

by jhofstede

search_food

Read-only

Find Dutch food products by name in the Mijn Eetmeter database and return the Id, Type, and SynonymId needed to add an entry to your diary.

Instructions

Search for food products by name in the Mijn Eetmeter database. Returns products with Id, Type and SynonymId, which add_food needs.

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": {
      "query": "<query>"
    },
    "name": "search_food"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesFood name to search for (Dutch)
product_typeNoFilter: 1=generic, 2=recipe, 4=branded. Omit for all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive and open-world, so the safety profile is covered. The description adds the return shape (Id, Type, SynonymId) and the downstream handoff, which is genuinely useful, but it says nothing about result limits, partial matching behavior, or empty-result handling for an open-world search.

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 short sentences with zero filler; the core action is front-loaded and the return/handoff note follows immediately.

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?

With no output schema, the description compensates by naming the returned fields and their purpose. It is complete enough to call correctly, though it omits any note on result volume or matching semantics for a search tool.

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 description coverage is 100%, so both query and product_type are already documented, including the enum-like 1/2/4 mapping. The description adds no further parameter meaning beyond what the schema supplies, so the baseline 3 applies.

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?

States a specific verb and resource ("Search for food products by name") plus the database it queries, and explicitly ties the output to the sibling that consumes it (add_food). An agent can distinguish it from add_food/delete_food/get_diary without opening any schema.

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 phrase "which add_food needs" gives a clear usage context — search first, then add — but it stops short of stating exclusions such as when to use get_favorites instead, or what to do when the search returns nothing.

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