Skip to main content
Glama

fetch_recipe

Read-only

Extract ingredients from a recipe page URL and get them parsed for your Bring shopping list. Use it to turn a recipe into list-ready ingredients, excluding pantry staples, before adding items.

Instructions

Extract the ingredients of a recipe page (with Bring's recipe parser).

pantry = ingredient usually already at home (salt, pepper...). Adds nothing to the list: adjust the quantities to the number of servings, then call add_items.

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": {
      "url": "<url>"
    },
    "name": "fetch_recipe"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesRecipe page URL
listNoBring list name (default: the main list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavior beyond that: the output is a parsed ingredient set, ingredients flagged as pantry (salt, pepper) should be excluded, and quantities must be rescaled before adding. Since there is no output schema, the pantry-output note is genuinely useful. It does not cover failure behavior for unparseable pages, so not a 5.

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?

Short and front-loaded, with the core action in the first clause. The second paragraph is a dangling fragment ("Adds nothing to the list") whose subject is unclear and which mixes the pantry rule with the add_items handoff, costing some clarity without padding length.

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?

With readOnlyHint covering the safety profile and no output schema, the description should carry the return shape, and it only gestures at it (ingredients plus a pantry classification) without saying what a result entry looks like. The scaling and handoff notes are helpful, but an agent still cannot predict the response structure or error cases.

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 description coverage is 100% (url as "Recipe page URL", list as "Bring list name (default: the main list)"), so the baseline is 3. The description only obliquely touches the list parameter via "Adds nothing to the list" and adds no format or syntax detail beyond the schema.

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 opens with a specific verb+resource: "Extract the ingredients of a recipe page," and clarifies the mechanism (Bring's recipe parser). It also states a negative scope ("Adds nothing to the list") that separates it from write tools like add_items. It stops short of naming a sibling it replaces, but the verb+resource is unambiguous.

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?

Clear usage context is given: fetch ingredients, account for the pantry rule, adjust quantities to servings, then hand off to add_items. That is a concrete workflow with the next tool named. It lacks explicit exclusions such as what to do when a URL is not a recipe page, which keeps it below a 5.

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