Cookidoo MCP Server

by herp75

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Create Collection

create_collection

Create a new empty custom collection on a Cookidoo account to organize recipes into a personal list.

Instructions

Create a new, empty custom collection on the user's account. Each call creates another collection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`name`	Yes	Collection name

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Nov 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish this is a non-read, non-destructive, open-world write, so the description only needs incremental context. 'Each call creates another collection' is a genuinely valuable add: it warns the agent the operation is non-idempotent and retries will produce duplicates. It still doesn't say how name collisions are handled or what happens if the name already exists.

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, front-loaded with the action and scoped with the non-idempotency caveat. No filler, no restating of the title, and every clause adds information.

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 there is only one simple parameter. The description covers scope, emptiness, and duplicate-creation risk. The remaining gap is error/conflict behavior for an existing name, which is minor for a single-field create.

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?

There is a single parameter, 'name', documented at 100% schema coverage including 1-200 length bounds, so the schema carries the semantics. The description adds nothing about naming constraints (uniqueness, duplicates) beyond what the schema states, so baseline 3 applies.

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?

Specific verb and resource with useful qualifiers: 'Create a new, empty custom collection on the user's account' tells the agent it makes an empty container scoped to the account, which distinguishes it from add_to_collection (populating) and list_collections (reading). It does not name a sibling explicitly, so it stops short of 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 implied rather than stated: create a collection when one doesn't exist. There is no explicit when-to-use/when-not-to-use guidance and no pointer to list_collections for checking existing collections. The caveat that repeated calls create duplicates is useful, but it is framed as behavior, not routing guidance.

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