mcp-marmiton

Search recipes

search_recipes

Read-onlyIdempotent

Search Marmiton for French recipes using a dish name or ingredient. Returns matching recipes with IDs and URLs to retrieve full details.

Instructions

Search Marmiton for recipes by free text: a dish, an ingredient, or both, for example 'tarte aux pommes' or 'poulet curry coco'. Marmiton is a French site, so French terms work best. Returns candidate recipes with the id and URL needed to read one with get_recipe. One call returns one page of results. Marmiton's robots.txt disallows paginating search results, so this server does not, and there is no page parameter: narrow the query instead of asking for more pages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum recipes to return from this page of results.
`query`	Yes	What to search for, in French, for example 'tarte aux pommes'.

Output Schema

TableJSON Schema

Name	Required	Description
`notes`	Yes
`query`	Yes
`source`	Yes
`results`	Yes
`result_count`	Yes
`total_available`	Yes	Recipes on this page before applying 'limit'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.1.0Sep 11, 2026
- 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"
+]
```
Changed6 schema fields changedAug 21, 2026
- addedOutput schema / properties / result_count / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / result_count / minimum
```
Added value: +-9007199254740991
```
- addedOutput schema / properties / results / items / properties / image_url / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / results / items / properties / image_url / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / total_available / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / total_available / minimum
```
Added value: +-9007199254740991
```
First observedv1.0.2Aug 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond annotations: results are candidate recipes, pagination is disallowed due to robots.txt, and the server intentionally has no page parameter. This materially helps the agent understand the tool's boundaries.

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?

Every sentence earns its place: purpose, language guidance, result contents, one-page behavior, and the pagination constraint. It is front-loaded with the core action and examples, then covers the key limitation.

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?

Given the output schema exists and annotations cover safety, the description is complete enough for correct invocation. It explains what the tool returns, how it connects to get_recipe, and the critical pagination constraint. No essential operational detail is missing.

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 baseline is 3. The description adds meaning beyond the schema by clarifying the query can be a dish, ingredient, or both, and by explaining the absence of a page parameter in relation to the one-page result behavior. The limit parameter is not described in prose, but the schema already documents it fully.

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?

States a specific verb and resource: 'Search Marmiton for recipes by free text'. Provides concrete examples and clarifies it returns candidate recipes with the id and URL needed for get_recipe, distinguishing it from the sibling tool.

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?

Gives clear usage context: free-text search, French terms work best, and one call returns one page. Explicitly explains the robots.txt constraint, why there is no page parameter, and instructs to narrow the query instead of paginating. Also routes to get_recipe for reading a specific recipe.

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

Deploy Server