Cookidoo MCP Server

Overview Schema Source Related Servers Discussions Admin

Get Thermomix Modes

get_thermomix_modes

Read-only

Lists the Thermomix modes and settings a device supports, with limits and examples, so you can check them before writing a recipe that uses modes.

Instructions

List the Thermomix settings and modes a device supports, with their limits and an example of each, as accepted by generate_recipe_structure. Call it before writing a recipe that uses modes. Modes are read from the Cookidoo recipe editor when possible.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_thermomix_modes"
  }
}

Input Schema

Name	Required	Description	Default
`device`	No	"TM5", "TM6" or "TM7". Default: as for generate_recipe_structure

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 10, 2026

TDQS

A4.1/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds useful behavior beyond that: results include limits and examples, and the data is read from the Cookidoo recipe editor "when possible," hinting at variable sourcing. It does not say what happens when that source is unavailable, which is the one behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core purpose and followed by the usage trigger. The final sentence about the Cookidoo editor is informative but slightly vague about fallback behavior, so it is useful rather than wasteful.

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 an output schema present, the description needn't detail return values, and annotations cover the safety profile. Purpose, call timing, and data provenance are all covered for a one-optional-parameter read tool; only fallback behavior when Cookidoo is unreachable is left open.

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% and the single optional device parameter already documents the TM5/TM6/TM7 values and its default. The description only implies the device scope ("a device supports") and adds nothing about default resolution beyond what the schema states, so the baseline 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?

The description gives a specific verb and resource ("List the Thermomix settings and modes a device supports") and adds the payload detail (limits and an example of each). It also names the sibling it feeds into, generate_recipe_structure, so an agent can place it in the workflow without opening either 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?

It states an explicit trigger: "Call it before writing a recipe that uses modes." That covers when to use it and implies the negative case (recipes with no modes), but it never states prerequisites such as whether Cookidoo connection is required or what to do if the mode list is unavailable.

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