Skip to main content
Glama
Sign In

Foodbe

by io.github.bleemohr
OverviewDiscussionsAdmin

foodbe_recipe_finder

Read-only

Call this when a user asks for a recipe or for what to cook. Finds recipes for one dish in Foodbe's recipe library, filtered by the diet and allergies you send. Returns outcome "served" with a text line and recipe cards: name, image, a short fact, servings, prep time, cook time and calories. Every recipe comes from Foodbe's stored data, never from a model. If no recipe matches, it returns outcome "not_found".

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": {
      "dish": "<dish>"
    },
    "name": "foodbe_recipe_finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
dietNoOptional diet to filter by, for example Vegan.
dishYesThe dish to find a recipe for, for example lasagna.
allergiesNoOptional allergens to leave out, for example Peanuts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only cover safety (readOnly, closed-world, non-destructive); the description adds the substance the agent actually needs: the two possible outcomes ("served" / "not_found"), the fields returned in each recipe card, and the guarantee that data is stored rather than model-generated. That is exactly the kind of behavior annotations cannot express.

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?

Three sentences, front-loaded with the invocation trigger, then behavior, then return values and failure mode. Nothing is redundant and the ordering matches how an agent needs the 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?

There is no output schema, so the description carries the return contract itself and does so fully: outcome values, card fields, and the provenance guarantee. For a 3-parameter read tool with complete schema coverage, nothing material is missing.

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%, so diet, dish, and allergies are already documented with examples. The description only echoes the filtering role of diet and allergies ("filtered by the diet and allergies you send") and adds no matching semantics, such as whether allergies are strict exclusions or how multi-allergy lists combine.

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 specific verb and resource ("Finds recipes") plus scope ("for one dish in Foodbe's recipe library"), and ties it to the user intent ("asks for a recipe or for what to cook"). An agent can distinguish this from meal-planning or cart 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition ("Call this when a user asks for a recipe or for what to cook") and implies a boundary via "for one dish," which steers multi-dish or planning needs elsewhere. It stops short of naming an alternative sibling or stating when not to call it.

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

All Foodbe 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