Cookidoo MCP Server

Overview Schema Source Related Servers Discussions Admin

Connect To Cookidoo

connect_to_cookidoo

Read-only

Authenticate with Cookidoo using environment or .env credentials. Use it to verify configuration or force a fresh login when other tools need a valid connection.

Instructions

Authenticate with Cookidoo using the credentials from the environment / .env file.

Optional: every other tool connects automatically on first use. Call this to check the configuration or to force a fresh login.

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

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

A4.3/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavioral context — that credentials are read from env/.env, that connection happens lazily elsewhere, and that this call can force a fresh login (i.e., it interacts with network/auth state). It does not cover what happens on failure or whether a session is invalidated, keeping it below a 5.

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 short sentences: the action and credential source first, then the optionality caveat and use cases. No filler, and the most decision-relevant fact (you usually don't need this) is easy to find.

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?

An output schema exists, so return values need no explanation, and the description covers credential sourcing, lazy auto-connect, and forced re-login. Minor gaps remain around failure behavior and which environment variables must be set, but nothing essential for correct invocation is missing.

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?

Zero parameters, so the baseline is 4. The description usefully explains that credentials come from the environment rather than from arguments, which is exactly the ambiguity an agent might have for a parameterless auth tool.

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 names a specific verb ('Authenticate') and resource ('Cookidoo') and states the credential source (environment / .env file). It is clearly the auth/session tool among a catalog of recipe and shopping-list siblings, though it does not explicitly name any sibling to contrast with.

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?

It gives explicit when-not guidance ('Optional: every other tool connects automatically on first use') and two concrete when-to-use cases (check configuration, force a fresh login). The implicit alternative — just call any other tool — is stated outright, leaving nothing to inference.

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