Skip to main content
Glama
Pantrist-dev

Pantrist

Official

search_recipes

Find recipes by free-text query and optional category filters. Get paginated results of your own creations and public favorites.

Instructions

Search the user's recipes (their own creations + public favourites) by free-text and optional category filters. Read-only and paginated — returns { results: RecipeDto[], totalCount, totalPages, currentPage }. To fetch a single recipe by uuid use get_recipe; to delete one you own use delete_recipe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchStringNoFree-text query matched against recipe name, description, and ingredient names. Case-insensitive. Omit to list all recipes (still paginated).
categoriesNoOptional category filter — multiple categories are OR-combined. Values must come from the recipe-categories enum (e.g. "Breakfast", "Vegetarian", "LowCarb").
currentPageNo1-based page index. Page size is fixed server-side. Defaults to 1.
Behavior4/5

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

The description declares the tool is read-only, paginated, and specifies the return shape. While no annotations are provided, it could be more explicit about page size limits or ordering, but it adequately covers core behavioral traits.

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 pack all essential information without wasted words: purpose, return format, and sibling references.

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?

Given no output schema, the description compensates by specifying the return structure. It covers all parameters and pagination. Could mention error handling or default page size, but overall sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds significant detail: free-text matching behavior (case-insensitive, fields searched), category OR-combination, and currentPage defaults and fixed page size.

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 clearly states the tool searches user recipes by free-text and category filters, differentiating itself from sibling tools like get_recipe and delete_recipe.

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?

It explicitly mentions when to use search_recipes versus alternatives (get_recipe for single lookup, delete_recipe for deletion), providing clear context for agent decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantrist-dev/pantrist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server