Skip to main content
Glama

Look up an ingredient

lookup_ingredient
Read-onlyIdempotent

Tell which allergens, if any, an ingredient name belongs to, e.g. "sodium caseinate" -> milk, "Prunus amygdalus dulcis oil" -> tree nuts, "DMDM hydantoin" -> formaldehyde releasers.

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": {
      "ingredient": "<ingredient>"
    },
    "name": "lookup_ingredient"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage of the text, if known, e.g. "fr". Optional; helps short words in other languages be read correctly.
ingredientYesOne ingredient name as printed on a label.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / language
      Added value: +{
      +  "description": "Language of the text, if known, e.g. \"fr\". Optional; helps short words in other languages be read correctly.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description's job is lighter. It still adds value beyond them: 'if any' signals the result may be empty, and the example pairs effectively preview the shape and vocabulary of the return value (allergen category names) despite there being no output schema.

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?

A single front-loaded sentence with the core behavior first, followed by three illustrative mappings that each earn their place by showing the input format and output vocabulary.

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?

For a simple two-parameter read-only lookup with rich annotations and no output schema, the description plus examples give enough to call it correctly. The main remaining gap is unspecified behavior for an unrecognized ingredient (empty result vs. unknown marker).

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 description coverage is 100%, so the schema already documents both the ingredient and optional language parameters. The examples do add meaning about input form — Latin/INCI names like 'Prunus amygdalus dulcis oil' are accepted — but the language parameter's role is left entirely to the schema.

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?

States a specific verb and resource: maps one ingredient name to the allergens it belongs to, with three concrete examples. It does not explicitly name sibling tools, but the singular 'ingredient name' framing is distinguishable from check_product_allergens (product-level) and list_supported_allergens (taxonomy listing).

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?

Usage is only implied: the tool is for looking up a single ingredient. There is no explicit when-to-use/when-not, and no routing to check_product_allergens for whole-product checks or list_supported_allergens for the allergen taxonomy, which an agent would have to infer from the sibling names.

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.