Skip to main content
Glama

Get a recipe as structured data

get_recipe
Read-only

Use this when you already know a recipe's slug and want structured JSON (ingredient quantities and units, steps, servings, nutrition) instead of prose, for example to scale quantities or build a shopping list.

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": {
      "slug": "<slug>"
    },
    "name": "get_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
localeNo

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
dateYes
tagsYes
tipsYes
titleYes
yieldYes
localeYes
categoryYes
servingsYes
nutritionYes
contentTypeYes
descriptionYes
procedureSectionsYes
ingredientSectionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered without prose. The description adds the useful behavioral fact that results come back as structured JSON rather than prose, but says nothing about what happens on an unknown slug, whether results are cached, or rate limits. With annotations carrying the safety burden, this is adequate rather than rich.

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?

A single front-loaded sentence that leads with the trigger condition and then the payoff, with no filler. It is slightly dense in its parenthetical field list, but every clause adds information.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the read-only lookup nature is simple enough that little behavioral disclosure is required. However, for a 2-parameter tool with 0% schema description coverage, omitting any mention of `locale` and any note on unknown-slug behavior leaves a real gap.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the parameter burden and it only partly does: it explains that a slug is a known identifier for the recipe, but never describes the expected format. The `locale` parameter (enum en/es/ca) is entirely unmentioned, leaving the agent no guidance on when or why to set the output language.

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+resource ('Get a recipe') and enumerates the payload contents (ingredient quantities and units, steps, servings, nutrition), so the agent knows exactly what comes back. It implies a distinction from lookup-style siblings by requiring a known slug, but never names 'search' or 'fetch' explicitly, so differentiation is inferential rather than stated.

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?

'Use this when you already know a recipe's slug' is a clear precondition that implicitly rules out this tool for discovery-style queries. It stops short of naming the alternative for the unknown-slug case, and lists use cases (scaling quantities, shopping list) that confirm the intent rather than constrain it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources