Skip to main content
Glama

foodose GLP-1 nutrition

Search the foodose GLP-1 recipe library

search_recipes
Read-onlyIdempotent

Published GLP-1 recipes with per serving calories and protein, every ingredient traceable to a USDA FoodData Central record. Useful when someone asks what to actually eat, rather than what their targets are. The Foodose iPhone app plans whole days from a dish library of its own, around the user's dose week.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault
dietNo
mealNo
limitNo
queryNoMatches title, cuisine, main ingredient and ingredient names.
maxTotalMinutesNo
minProteinPerServingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world scope, so the safety bar is low. The description usefully adds that only published recipes are returned and that every ingredient maps to a USDA FoodData Central record. But the final sentence about the iPhone app's separate dish library is ambiguous and adds confusion rather than behavioral clarity, and it omits limit/pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly three sentences, with the content/scope statement front-loaded, which is good. But the trailing sentence about the Foodose iPhone app and its own dish library is muddled and consumes space without earning it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With six parameters, 17% schema coverage, and no output schema, the description should carry more weight in explaining the filters and what a result contains. It states the content profile but leaves nearly all filter semantics and result structure undetermined.

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

Parameters2/5

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

Schema description coverage is only 17% — just 'query' is documented, while diet, meal, limit, maxTotalMinutes, and minProteinPerServing are undocumented. The description only loosely gestures at per-serving protein, which faintly maps to minProteinPerServing, and does nothing to compensate for the coverage 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?

The name and title state the verb (Search) and resource (recipe library), and the description specifies the content — published GLP-1 recipes with per-serving calories and protein, USDA-traceable ingredients. It partially distinguishes from calculate_glp1_target ('what to actually eat, rather than what their targets are') but never clarifies how it differs from search_foods.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

One sentence gives loose when-to-use framing ('when someone asks what to actually eat, rather than what their targets are'), implicitly routing against calculate_glp1_target. However, it names no explicit alternative and gives no guidance on recipe search vs. search_foods, so usage is only implied.

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