Skip to main content
Glama
Sign In

LastList

by com.lastlistapp
OverviewDiscussionsAdmin

Get recipe details

get_recipe
Read-only

Get full detail for one recipe by its recipeId: ingredients (name, quantity, unit), the kitchen tools it needs, servings, timing, cuisine, and dietary tags. Use after search_recipes to inspect a specific recipe the user picked. Tools tiered 'specialty' are the ones a typical kitchen may not have — worth mentioning before the user commits to the recipe.

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

Input Schema

NameRequiredDescriptionDefault
recipeIdYesThe recipeId from a search_recipes result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A5/5.0
Behavior5/5

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

While the annotations cover the safety profile (readOnlyHint), the description adds unique behavioral/business context: detailing what specific data points are returned (e.g., 'kitchen tools,' 'dietary tags') and providing a crucial warning about 'specialty' tools and the user commitment.

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?

The definition is structured perfectly: it states the goal, defines the input mechanism, gives usage context, and ends with a high-value behavioral advisory note. It is highly dense with relevant information.

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 that there is no output schema and only one input parameter, the description is fully complete. It informs the agent exactly what to expect in the return value and when to invoke the tool relative to its workflow peers.

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?

Although the schema coverage is 100%, the description adds vital semantic context by defining the source of the ID ('The recipeId from a search_recipes result') and comprehensively listing the output data types (ingredients, tools, etc.), which goes beyond just describing the input field.

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 retrieves 'full detail for one recipe' and specifies the components returned (ingredients, tools, servings, etc.). It explicitly names the function and the required identifier (recipeId).

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 provides a perfect workflow guideline: 'Use after search_recipes to inspect a specific recipe the user picked.' This completely defines the correct sequence of tool use relative to siblings.

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

All LastList toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources