Skip to main content
Glama

Fetch a full recipe

fetch
Read-only

Use this to retrieve the complete recipe (ingredients with quantities, steps, tips, nutrition) for an id returned by search.

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": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered structurally. The description adds that the result is the *complete* record and lists the sections included, which is genuine value, but it says nothing about failure modes (e.g. unknown id) or size of the response. Adequate but not rich, given annotations do the heavy lifting.

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?

One sentence, front-loaded with the action and back-loaded with the concrete return contents. No filler, no restatement of the title.

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?

A one-parameter read tool with an output schema and full annotation coverage; the description supplies the workflow context and the payload summary, which is everything needed to invoke it correctly. Return-value structure is already covered by the output schema.

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 0% — the single `id` parameter is an undescribed string. The description partially compensates by telling the agent the id's provenance (returned by `search`), which prevents guessing, but it gives no format hints or validation behavior. It adds meaning beyond the bare schema without fully closing the gap.

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?

Names a specific verb (retrieve) and resource (the complete recipe) and enumerates the payload (ingredients with quantities, steps, tips, nutrition), so an agent knows exactly what it gets back. It does not distinguish itself from the sibling `get_recipe`, leaving some ambiguity about which to pick, but the primary purpose 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?

Gives a clear triggering condition: use it with an id returned by `search`, which ties the tool into a two-step search-then-fetch workflow. It stops short of stating exclusions or naming an alternative for other lookup patterns, so it stops at 4 rather than 5.

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