Skip to main content
Glama
mcp-ptitchef

mcp-ptitchef

Browse a category or a standing list

browse_recipes
Read-onlyIdempotent

Browse recipes by Ptitchef category or standing list (latest, top-rated, most-viewed), page by page, to find dishes without an API key.

Instructions

Read the recipes under one category of Ptitchef, page by page, or one of the lists the site keeps standing. Pass 'category' with a slug from list_categories or from a search's 'topic_slug', or pass 'listing' for one of: latest, top_rated, most_viewed. Never build a category slug by hand: the site writes them freely and answers an address it does not hold by serving another page. The page in the answer is the one the site served. A page past the last one comes back either as the first page again or as not_found naming it past the last page.

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

Input Schema

NameRequiredDescriptionDefault
pageNoThe page of a category to read. A standing list has one page only.
limitNoRows to render, 20 by default.
listingNoOne of the site's standing lists, read instead of a category.
categoryNoA category slug: one from list_categories whose 'is_family' is false, or the 'topic_slug' a search answered with. A family's slug belongs to list_categories instead.

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.5/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them by disclosing two non-obvious site behaviors: an unrecognized address silently serves a different page, and a page past the last comes back as either the first page again or a not_found naming it past the end. That is high-value information an agent cannot infer from structured fields.

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?

Front-loaded with the two addressing modes, then the sourcing rule, then the paging caveat — no filler sentences. Slightly dense in the closing sentence, and 'The page in the answer is the one the site served' is a touch cryptic for the value it delivers.

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 present the description needn't explain return values, and it covers the site quirks and slug sourcing well. The gap is that all parameters are optional, yet the description never says what happens with no arguments or with both 'category' and 'listing' set.

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%, so all four parameters are already documented, including the category slug's provenance and the listing enum. The description restates the slug sources and adds the hand-built-slug warning, but adds no new semantics for 'page' or 'limit' and never states what happens if both category and listing are supplied or neither is. 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?

Specific verb+resource: reading recipes under one category page by page, or one of the site's standing lists. It clearly separates the two addressing modes (category slug vs listing) and is distinguishable from list_categories, search_recipes, and get_recipe 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: take 'category' from list_categories or a search's 'topic_slug', or use 'listing' with one of three named values. It adds a firm when-not ('Never build a category slug by hand') with the reason, which is exactly the kind of alternative-selection guidance that prevents wrong calls.

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