Skip to main content
Glama
mcp-ptitchef

mcp-ptitchef

Search recipes

search_recipes
Read-onlyIdempotent

Search Ptitchef recipes by dish or ingredient in French to find matching category pages or single-page results, with totals indicating whether dishes were found.

Instructions

Search recipes on Ptitchef by dish or ingredient. The site answers in one of two ways and the answer says which: it either sends the search to a category page of its own, whose total counts what that category holds, or it answers on its own terms on a single page whose total is the number of rows served. When a category answered, 'topic_slug' names it and browse_recipes reads its further pages. Some topics come back as a guide the site wrote instead, grouped under headings of its own and carrying no total; browse_recipes on the same 'topic_slug' reads their full listing. A search the site matched nothing for comes back with no row and a total of zero, which is an absence the site stated.

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": {
      "query": "<query>"
    },
    "name": "search_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to render, 20 by default. 'rows_seen' states what the page served.
queryYesA dish or an ingredient, in French, as a reader of the site would type it.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, and the description goes further by disclosing that the site answers in two structurally different ways (category page vs. single page vs. heading-grouped guide) and that totals mean different things in each. That is genuine behavioral context an agent cannot get from the annotations, though it overlaps somewhat with what the output schema likely documents.

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

Conciseness3/5

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

Purpose is front-loaded in the first sentence, but the remainder is a dense, clause-heavy run-on that forces the reader to untangle nested conditionals. Phrases like 'which is an absence the site stated' are longer than the meaning they carry.

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 an output schema, full parameter coverage, and rich annotations, the description fills the gaps that matter: the two response branches, the meaning of totals, and the zero-result case. The only meaningful omission is sibling differentiation against search_by_ingredients.

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?

Schema coverage is 100% and both parameters are already documented, including the French-language constraint on 'query' and the default row count. The description adds no parameter-level detail; its mention of 'topic_slug' refers to an output field, not an input, so the 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?

The first sentence gives a specific verb and resource ('Search recipes on Ptitchef by dish or ingredient') and the rest explains the two result modes. It partially differentiates from siblings by naming browse_recipes as the pagination path, but never clarifies how it differs from search_by_ingredients, which is a close-sounding sibling.

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?

It states explicit follow-up conditions: when a category answered, use browse_recipes on 'topic_slug' for further pages, and the same for guide-style topics. It also tells the agent how to read a zero-row/zero-total answer. The missing piece is any guidance on choosing this tool over search_by_ingredients.

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