Thermomix-MCP

find_recipe_image

Searches for a matching recipe photo as a fallback when a recipe lacks its own image. Uses a concrete search term and requires a PEXELS API key.

Instructions

Sucht ein passendes Gerichtsfoto (Fallback, wenn das Rezept kein eigenes Bild hat).

Bevorzuge immer das image_url aus fetch_recipe. Kurzer, konkreter Suchbegriff (z.B. "Kürbissuppe Teller"). Braucht einen PEXELS_API_KEY in der .env.

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": "find_recipe_image"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

A4.6/5.0

Behavior4/5

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

The description discloses that it requires a PEXELS_API_KEY in the .env file, which is important for the agent to know. However, it does not specify rate limits, error behavior, or details about the external API call. With no annotations, the description carries the full burden; the key disclosure adds value.

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 three sentences, efficiently front-loading the purpose and then providing usage guidance and parameter advice. No unnecessary words.

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 a simple tool with one parameter and an existing output schema, the description covers purpose, usage guidelines, parameter semantics, and an environment requirement. It is sufficiently complete for an agent to use correctly.

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

Parameters4/5

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

The input schema has a single string parameter 'query' with no description (0% coverage). The description compensates by advising a 'short, concrete search term' with an example, adding meaning beyond the schema.

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 tool's purpose: searching for a matching dish photo as a fallback when the recipe has no own image. It distinguishes itself from siblings like fetch_recipe by positioning this as a fallback.

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

Usage Guidelines5/5

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

Explicit guidance is given: first prefer the image_url from fetch_recipe, and only use this tool as fallback. Also provides an example of a concrete search term.

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

Deploy Server