Cookidoo MCP Server

by herp75

Overview Schema Source Related Servers Discussions Admin

Python

Remote

List Devices

list_devices

Read-only

Retrieve the Thermomix devices linked to a Cookidoo account to identify available models such as TM6 or TM7.

Instructions

List the Thermomix devices linked to the Cookidoo account (e.g. TM6, TM7).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 10, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe-read profile is covered without the description repeating it. The description adds account scoping and device-type examples, but says nothing about authentication requirements (e.g. an established Cookidoo connection) or empty-result behavior, which would matter for a list call against a remote account.

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?

A single sentence that front-loads the verb and resource and uses a parenthetical only to make the resource concrete. Nothing is redundant or padded.

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 zero-parameter read tool with an output schema and clear safety annotations, the description covers the essentials. The one meaningful omission is that it does not state the dependency on an active Cookidoo account connection, which an agent would otherwise have to discover from errors.

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 tool takes zero parameters and the schema is empty, so there is no parameter meaning to add or omit. The baseline of 4 applies; the description does not need to explain any inputs.

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 gives a specific verb and resource ('List the Thermomix devices linked to the Cookidoo account') and clarifies the resource with concrete examples (TM6, TM7), so there is no ambiguity about what is returned. It does not explicitly differentiate itself from adjacent tools such as get_account_info or get_thermomix_modes, which keeps it below a 5.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for enumerating linked hardware, but there is no statement of when to prefer it over siblings, nor any prerequisite such as being connected to Cookidoo. For a zero-parameter read tool the cost of this gap is small, but the guidance is not explicit.

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