Skip to main content
Glama

Search Bevel's food database

bevel_search_food
Read-only

Search generic and branded foods to get fdbId, serving options and per-serving calories and macros, then log the item with bevel_log_food.

Instructions

Searches foods the way the app does (generic + branded, 5 each). Returns fdbId, serving options and per-serving calories, protein, carbohydrate, fat, fiber, sugar and caffeine. Use an fdbId from here with bevel_log_food.

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

Input Schema

NameRequiredDescriptionDefault
queryYesFood name, e.g. 'banana' or 'greek yogurt'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-lookup nature are covered. The description adds genuinely new behavior: a capped result set (5 generic + 5 branded) and the exact per-serving nutrient fields returned. It stops short of describing matching semantics (fuzzy vs exact) or how ranking works, which matter for a search tool.

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 tight sentences with zero filler, front-loaded with the result-shape clause, then the return fields, then the sibling handoff. Every sentence contributes information an agent would otherwise have to discover by trial.

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

Completeness4/5

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

With no output schema, the description correctly enumerates the returned fields and the fdbId key needed for downstream calls. Given a one-parameter, read-only search tool this is nearly sufficient; only matching/ranking behavior and empty-result handling are left implicit.

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% and the single parameter already carries a description with examples ('banana', 'greek yogurt'), so the schema does the work. The description adds no guidance on query phrasing, partial names, or branded-name matching beyond what the schema states. Baseline 3 applies.

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 ('Searches foods'), plus a concrete scope: generic + branded, five results each. That result-shape detail lets an agent distinguish this as the discovery step in the food workflow without opening the schema.

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?

The handoff sentence ('Use an fdbId from here with bevel_log_food') implies the search-then-log flow, which is useful. However there is no explicit when-not guidance, no note on what to do when a query returns nothing or the desired food is missing, and no mention of the 10-result ceiling as a reason to refine the query.

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