Skip to main content
Glama

Find a recipe by link

find_recipe
Read-onlyIdempotent

Use this when the user shares a recipe link and you only need to know whether Only Recipes already has it. Returns the matching recipe's id, name and page, or exists: false. Fetches nothing. To show the recipe, use import_recipe instead.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe recipe's original web address

Output Schema

NameRequiredDescriptionDefault
existsYes
recipeIdNo
recipeUrlNo
recipeNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description still adds genuinely new behavior: it performs no network fetch ('Fetches nothing') and returns a sentinel 'exists: false' rather than erroring on a miss, which is not derivable from the annotations. Minor deduction because the return-field listing overlaps the output schema.

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?

Four short sentences, front-loaded with the usage condition, then the return contract, then the exclusion and sibling pointer. Every sentence carries distinct information with no filler.

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?

For a one-parameter read-only lookup with a declared output schema and full annotation coverage, nothing an agent needs is missing. The miss case, the no-fetch behavior, and the routing to import_recipe are all covered.

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% with a single documented 'url' parameter (URI format), so the schema carries the load and the baseline is 3. The description only restates it as 'a recipe link' and adds no guidance on URL normalization, tracking parameters, or whether relative/redirected links are acceptable.

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?

States a precise purpose: an existence check against Only Recipes for a shared recipe URL, returning 'the matching recipe's id, name and page, or exists: false'. The scope ('only need to know whether') and the explicit contrast with import_recipe let an agent distinguish it from siblings without opening a schema.

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?

Gives both the triggering condition ('when the user shares a recipe link and you only need to know whether Only Recipes already has it') and the alternative for the other case ('To show the recipe, use import_recipe instead'). The negative constraint 'Fetches nothing' further rules out using it as a retrieval tool.

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