ask.recipes

Connect Cookidoo (Thermomix / Bimby)

connect_cookidoo

Idempotent

Check whether the user's Cookidoo account (the Thermomix / Bimby recipe platform) is connected, and when it is not, return a one-time link where they enter their Cookidoo login. For "connect my Thermomix", "link my Bimby", or before the first send_to_thermomix. Give the user the link; it works once and expires in 15 minutes.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`email`	No
`units`	No	units the Thermomix works in
`devices`	No	every Thermomix paired with the account
`machine`	No	Thermomix model the recipes are written for
`language`	No	language of the Cookidoo account; write everything sent to it in this language
`username`	No
`connected`	Yes
`last_error`	No
`connect_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / devices

Added value: +{
+  "description": "every Thermomix paired with the account",
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / machine / description

Added value: +"Thermomix model the recipes are written for"

Changed2 schema fields changedOct 20, 2026

addedOutput schema / properties / language

Added value: +{
+  "description": "language of the Cookidoo account; write everything sent to it in this language",
+  "type": "string"
+}

addedOutput schema / properties / units

Added value: +{
+  "description": "units the Thermomix works in",
+  "type": "string"
+}

AddedOct 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Adds real behavior beyond the annotations: the returned link is one-time and expires in 15 minutes, and the user—not the tool—enters credentials. That explains why the tool is non-destructive yet not readOnly (it mints a session). It does not say what the response looks like when already connected or whether the agent must re-poll after the user completes the flow, leaving a small gap.

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 core action, then triggers, then the operational caveat about expiry. No filler and nothing repeated from the title or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with an output schema, the description covers everything an agent needs: when to call it, what the user must do, and how long the returned artifact is valid. Return-value details are appropriately delegated to the output schema.

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, so there is nothing for the description to disambiguate and the baseline applies. Calling convention is fully determined by the tool name and description.

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 concrete verb and resource ('Check whether the user's Cookidoo account ... is connected') plus the fallback behavior (returns a one-time login link). It disambiguates from siblings by naming the Thermomix/Bimby alias and by implying this is the entry point rather than the actual import/send operations handled by other tools.

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?

Gives explicit trigger phrases ('connect my Thermomix', 'link my Bimby') and a concrete sequencing rule ('before the first send_to_thermomix'), naming the sibling that depends on it. It also tells the agent to hand the link to the user, so the invocation context is unambiguous.

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

All ask.recipes tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.