Skip to main content
Glama

get_ingredient_nutrition

Read-only

Per-100g nutrition (calories, protein, carbs, fat) for raw ingredients, from the platform's curated table. Call this while building a diet plan to itemise each meal into real raw materials with real quantities, instead of guessing per-food macros. Query by plain name ('paneer', 'cooking oil', 'toor dal'); results are ranked by matchConfidence and include a typicalServingG anchor and an isCookingAddition flag. Scale the per-100g figures to your chosen quantity (e.g. 60 g paneer = 60% of the per-100g values). If an ingredient isn't found, estimate sensibly and still list it — never drop the cooking fat.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / limit / default
      Added value: +5
    • removedInput schema / properties / limit / description
      Removed value: -"Matches per name (default 3, or 2 per name with queries)."
    • changedInput schema / properties / limit / maximum
      Previous value: -10New value: +20
    • removedInput schema / properties / queries
      Removed value: -{
      -  "description": "Several ingredient names in one call; returns the top matches for each.",
      -  "items": {
      -    "minLength": 1,
      -    "type": "string"
      -  },
      -  "maxItems": 40,
      -  "type": "array"
      -}
    • addedInput schema / required
      Added value: +[
      +  "query"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries the substantive load and does: it discloses the data source (curated table), result ordering (ranked by matchConfidence), extra return fields (typicalServingG anchor, isCookingAddition flag), and a fallback policy on misses. The only gap is that the meaning of the limit parameter and the shape of the ranked result list are left implicit.

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

Conciseness4/5

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

Front-loaded with the purpose sentence, then usage, then output semantics, then the failure rule — a sensible order. Slightly verbose in places ("real raw materials with real quantities") and the scaling example restates the obvious, but nearly every sentence carries information.

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 does the needed work by naming the key return fields and their role, and it explains the scaling step an agent must apply. The unexplained limit parameter and the absence of any note on result size or empty-result shape keep it short of complete.

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 0%, so the description must compensate for both parameters. It does well for query, giving plain-name syntax and three examples ('paneer', 'cooking oil', 'toor dal'), but says nothing about limit beyond the schema's default/maximum — an agent cannot tell whether it caps ranked matches or something else.

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?

Opens with a specific resource and unit basis: per-100g nutrition (calories, protein, carbs, fat) for raw ingredients from the platform's curated table. An agent can immediately tell this is a nutrition lookup, not a logging or plan-mutation tool, which separates it from the get_client_* siblings.

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?

States the triggering context explicitly ("Call this while building a diet plan to itemise each meal into real raw materials") and contrasts it with the wrong behaviour ("instead of guessing per-food macros"). It even handles the failure path: if an ingredient isn't found, estimate and still list it, never drop the cooking fat.

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.