Skip to main content
Glama
Sign In
Unofficial Monsieur Cuisine MCP

Unofficial Monsieur Cuisine MCP

by githubllff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Cookidoo Login

cookidoo_login

Logs in to Cookidoo and caches the authentication token, enabling Cookidoo recipes to be imported in later calls.

Instructions

Log in to Cookidoo (Thermomix's official recipe platform) and cache the auth token, so Cookidoo recipes can be imported afterwards.

Credentials can be passed explicitly here, or set once via the COOKIDOO_EMAIL / COOKIDOO_PASSWORD environment variables (and optionally COOKIDOO_COUNTRY, default 'gb', and COOKIDOO_LANGUAGE, default 'en-GB') in a .env file in the project root. The token is cached in .cookidoo_token and reused on later calls.

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

Input Schema

NameRequiredDescriptionDefault
emailNoCookidoo account email (optional if set via env/.env).
countryNoCookidoo country code, e.g. 'gb', 'de', 'es' (default 'gb').
languageNoCookidoo language code, e.g. 'en-GB', 'de-DE' (default 'en-GB').
passwordNoCookidoo account password (optional if set via env/.env).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden, and it does disclose a real side effect: a token file is written to .cookidoo_token and reused later, plus the credential sourcing order (explicit args vs. env/.env). It omits failure behavior, whether an existing token is overwritten, and any auth/rate-limit constraints on the login request itself.

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 tight paragraphs: the action and its purpose first, then the configuration mechanics. Every sentence carries information an agent needs (token location, env var names, defaults) with no filler.

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 no-annotation auth tool with an output schema, the description covers what it does, what it persists, where credentials come from, and defaults. The remaining gap is error/expiry behavior on invalid credentials, which an agent would need if the login fails mid-workflow.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds value beyond the schema by naming the concrete environment variables (COOKIDOO_EMAIL, COOKIDOO_PASSWORD, COOKIDOO_COUNTRY, COOKIDOO_LANGUAGE), the .env-in-project-root convention, and the defaults, which the schema only alludes to generically.

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 ('Log in to Cookidoo') plus the second effect ('cache the auth token') and the downstream reason ('so Cookidoo recipes can be imported afterwards'). That last clause implicitly distinguishes it from sibling import_cookidoo_recipe, which consumes the token rather than creating it.

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?

Gives clear context: call this before importing Cookidoo recipes, and note that the cached token is reused on later calls, which implies you need not call it every time. It does not explicitly point at cookidoo_status as the way to check whether a valid token already exists, nor state what happens on repeated calls with a stale token.

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

Deploy Server

Other Tools