Unofficial Monsieur Cuisine MCP

Overview Schema Source Related Servers Discussions Admin

List Paprika Recipes

list_paprika_recipes

Preview a Paprika export archive by listing each recipe's name, servings, difficulty, categories, and photo status before converting or importing it to Monsieur Cuisine.

Instructions

List the recipes inside a Paprika app export archive (.paprikarecipes.zip).

Read-only preview of what the export contains: one entry per recipe with its name, servings, difficulty, Paprika categories and whether it has an embedded photo. Use get_paprika_recipe to preview the full Monsieur Cuisine conversion of one recipe, or import_paprika_recipes to create and publish them on the user's account.

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": {
      "zip_path": "<zip_path>"
    },
    "name": "list_paprika_recipes"
  }
}

Input Schema

Name	Required	Description	Default
`zip_path`	Yes	Path to the .paprikarecipes.zip export file (e.g. from Paprika's "Export all recipes").

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, but the description carries most of the burden itself by declaring the operation read-only and enumerating the returned fields (name, servings, difficulty, categories, photo flag). It leaves out what happens on a missing or malformed archive, which is the main remaining behavioral gap for a file-path tool.

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 sentences, zero waste, and the identifying purpose is front-loaded before the return contents and the sibling routing. Each sentence earns its place.

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?

With one well-documented required parameter and an output schema present, the description needn't explain return shape — yet it still summarizes entry contents helpfully. Only missing element is error/failure behavior for invalid archives.

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?

The single zip_path parameter has 100% schema description coverage including an example source (Paprika's "Export all recipes"), so the schema does the work. The description only reinforces the file type in prose and adds no path format, relative-vs-absolute, or size guidance beyond the schema — baseline 3 is appropriate.

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 ("List the recipes inside a Paprika app export archive") with the exact file type (.paprikarecipes.zip). The second sentence defines what each listed entry contains, and the third names the two related siblings, so an agent can distinguish it from get_paprika_recipe and import_paprika_recipes without opening schemas.

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?

Explicitly frames this as a preview/discovery step and routes to alternatives by condition: get_paprika_recipe for full conversion of one recipe, import_paprika_recipes to create and publish. Both the when-to-use and the when-to-use-something-else cases are covered.

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