Skip to main content
Glama
mcp-ptitchef

mcp-ptitchef

List the categories recipes are browsed by

list_categories
Read-onlyIdempotent

Lists Ptitchef recipe category families and subcategories with exact slugs, so you can browse or build category pages without guessing URLs.

Instructions

List the categories Ptitchef browses its recipes by. Called without arguments it returns the families of ingredients; pass a family's slug as 'family' to list the categories it holds. Read this before building an address by hand: the site writes its slugs freely, so the same vegetable appears as 'chou-kale' on one line and as 'recette-de-petits-pois' on the next, and a slug that was guessed lands on a page the site does not hold. Each entry carries the slug to pass back and the page to open.

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

Input Schema

NameRequiredDescriptionDefault
limitNoEntries to render, 20 by default and 200 at most. A level holding more than this says so, and 'categories_published' always states what the page listed.
familyNoThe slug of a family to open, taken from a previous call. Leave it out to read the families themselves, which is where the tree starts.

Output Schema

NameRequiredDescriptionDefault
urlYesThe page these categories were read from.
notesYes
familyYesThe family that was opened, or null for the root.
sourceYes
categoriesYes
family_titleYesThe site's own heading for this level. Null when the page carries none.
category_countYesEntries rendered here.
categories_publishedYesEntries the page listed, before any were rendered.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.1.0
    • removedOutput schema / properties / categories / items / properties / description / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / categories / items / properties / description / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / family / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / family / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / family_title / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / family_title / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observedv1.0.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety surface is covered. The description adds meaningful behavior beyond that: slugs are freely written, guessed slugs land on pages the site does not hold, and entries return the slug to pass back plus the page to open.

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 purpose, then the two call modes, then the caution and the return shape — a logical order with little waste. The concrete slug examples cost a few words but justify themselves by making the pitfall vivid.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only listing tool with a full output schema and complete annotations, nothing an agent needs is missing: both modes, the ordering constraint on slugs, and the returned slug/page pairing are all covered.

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 contributes by framing `family` as a round-trip value taken from a previous call and by explaining what an omitted `family` yields. It adds workflow meaning rather than merely restating the schema.

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?

A specific verb and resource ('List the categories Ptitchef browses its recipes by') plus both operating modes make the tool's function unambiguous. It stops short of naming how it relates to siblings like browse_recipes, but the taxonomy-listing role is still clear without opening a schema.

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?

Explicitly states the no-argument mode versus the 'family' mode and tells the agent to read this before hand-building an address, which is real when-to-use guidance. It does not name competing siblings or state when not to use it, so it falls short of a 5.

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