Skip to main content
Glama
Tandoor Recipes MCP

Tandoor Recipes MCP

List related recipes

related_recipes
Read-onlyIdempotent

List recipes similar to a given recipe by ID. Returns slim id and name results by default, or the full API response when detail is needed.

Instructions

List recipes related to this one (Tandoor similarity). Slim by default (id + name); pass format="full" for raw API response.

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": {
      "id": "<id>"
    },
    "name": "related_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRecipe ID
formatNoResponse detail level. Default "slim".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.4.4
    • addedInput schema / properties / id / description
      Added value: +"Recipe ID"
  2. First observedv3.4.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, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful non-obvious context: results are slim by default with only id and name, and format="full" returns the raw API response, which tells the agent what it will actually receive.

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?

Two compact sentences, front-loaded with purpose and immediately followed by the response-format switch. Nothing is redundant and the format guidance arrives before the agent needs to choose a value.

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 no output schema, the description carries the return-value burden and does so by naming the slim shape (id + name) and the full/raw fallback. It is not fully complete because result count and ordering of the similarity match are never stated.

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 both parameters are already documented, making 3 the baseline. The description does add meaning the schema lacks by explaining what slim versus full actually return, but it leaves the similarity ranking (how many results, what order) undefined.

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 description gives a specific verb and resource ("List recipes related to this one") and pins the relation to recipe similarity, which separates it from generic siblings like list_recipes or search_recipes. It stops short of naming an alternative explicitly, so an agent must infer the boundary rather than read it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by "related to this one" – call it when you already hold a recipe id and want similar ones – but there is no stated when-not, no mention of how many results come back, and no pointer to list_recipes/search_recipes for non-similarity lookups.

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