Skip to main content
Glama
mcp-ptitchef

mcp-ptitchef

Find recipes from the ingredients a cook has

search_by_ingredients
Read-onlyIdempotent

Search Ptitchef recipes by one to five ingredients you already have, named in French, and return a set number of matching results.

Instructions

Find Ptitchef recipes from the ingredients a cook already has. Give one to 5 ingredients in French, as a cook would name them ("poulet", "citron"). The site counts every recipe it finds and serves one page of them, so 'total_available' can be far larger than the rows returned, and the rest cannot be reached. A longer list than the site's own form reads is refused rather than sent and silently cut.

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": {
      "ingredients": "<ingredients>"
    },
    "name": "search_by_ingredients"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to render, 20 by default.
ingredientsYesOne to 5 ingredients, in French. The site reads no more than that.

Output Schema

NameRequiredDescriptionDefault
urlYesThe address the listing was read from.
kindYesHow the listing came to be, which decides what its total counts. 'topic' means the site answered a search from a page of its own; 'free_text' means it answered on its own terms.
pageYesThe page that was read, which is the one the site served.
askedYesWhat was asked for: a search, a category, or a list of ingredients. 'query' carries the same value under the name every source of recipes publishes it in.
notesYesWhat qualifies this answer: what its total counts, what it left out, and where the site answered from an address other than the one asked for. Read these before quoting a figure.
queryYesWhat was asked for, under the name a search publishes it in.
titleYesThe site's own heading for the listing.
foldedYesRows naming a recipe already held. A guide lists one recipe under two headings where it belongs to both; such a row is counted in 'rows_seen' and rendered once.
sourceYesThe site this answer was read from. Credit it when showing a row.
resultsYes
rows_seenYesRows the site served on this page, before any were set aside.
topic_slugYesThe category page this listing was served from. Pass it to browse_recipes as 'category' to read the topic's further pages, and its total where this answer carries none.
single_pageYesTrue when the site serves this listing on one page and offers no further one.
result_countYesRows rendered here.
total_availableYesRecipes the site says this listing holds. Null when it published no figure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed16 schema fields changedv1.1.0
    • removedOutput schema / properties / results / items / properties / calories / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / calories / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / category / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / category / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / difficulty / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / difficulty / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / image_url / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / image_url / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / ingredients_preview / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / ingredients_preview / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / results / items / properties / rating / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / results / items / properties / rating / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / topic_slug / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / topic_slug / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses critical behavior: the site counts every matching recipe but serves only one page, so total_available can greatly exceed returned rows and the remainder is unreachable. It also explains that an oversized ingredient list is refused outright rather than silently truncated, which materially affects how an agent should call it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded: purpose first, then input guidance, then behavioral caveats. Every sentence contributes useful information, though the final sentence about refusal is slightly convoluted and could be more plainly stated.

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 formatting need not be explained, and the description wisely focuses on the non-obvious pagination limitation that total_available may exceed reachable rows. The main gap is the lack of explicit comparison with sibling search tools, but otherwise the agent has what it needs to call this correctly.

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. The description still adds semantic guidance beyond the schema by emphasizing French, cook-style ingredient names with examples such as 'poulet' and 'citron', helping the agent format values correctly.

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?

The description opens with a specific verb and resource: 'Find Ptitchef recipes from the ingredients a cook already has.' It clearly identifies an ingredient-driven search, which an agent can distinguish from sibling tools like search_recipes or browse_recipes without opening any schema.

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?

It specifies important usage constraints: one to five ingredients, in French, named as a cook would name them. However, it does not explicitly say when to choose this tool over search_recipes, browse_recipes, or list_categories, leaving the selection context implied rather than stated.

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