Skip to main content
Glama

Search Catalan and Spanish recipes

search
Read-only

Use this when the user wants Catalan, Spanish, or Mediterranean recipes or cooking ideas: dishes, desserts, breads, sauces, preserves, drinks, or techniques. Searches 470+ tested recipes by dish name, ingredient, or tag, in English, Spanish, or Catalan. Returns up to 10 results; call fetch with a result id for the full 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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
resultsYes

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?

The annotations already establish that this is a read-only, closed-world search. The description adds useful behavior beyond that: the corpus size, multilingual coverage, and a result cap of 10, plus the next step for getting a full recipe.

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 front-loaded with the usage condition and stays to two dense sentences. Every clause contributes scope, behavior, or next-step guidance without repetition.

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 search tool with annotations and an output schema, this is complete enough to invoke correctly. It covers domain scope, supported query dimensions, result limits, and the path to full recipe details.

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

Parameters4/5

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

Schema coverage is 0%, so the description must explain the single `query` parameter. It does so by saying searches can target dish names, ingredients, or tags in English, Spanish, or Catalan, though it does not specify matching rules or query syntax.

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 states a specific verb and resource: it searches 470+ tested Catalan, Spanish, or Mediterranean recipes. It scopes the corpus to dishes, desserts, breads, sauces, preserves, drinks, and techniques, and separates the search result from the full recipe retrieved by `fetch`.

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?

It gives an explicit triggering condition: use this when the user wants Catalan, Spanish, or Mediterranean recipes or cooking ideas. It also names the follow-up alternative, calling `fetch` with a result id for the full recipe, but does not state when not to use 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