Skip to main content
Glama

Get ingredient

get_ingredient
Read-onlyIdempotent

Finds a substance by name, form, synonym or ID. Omega-3 and fish oil identify EPA and DHA separately. Returns forms and the applicable country limit, then other countries’ limits with their scope, sources and recorded dates where available. Use detail "full" for form details, references and a link to search published products. Reference data only: it does not cover medication interactions, diagnosis or treatment decisions.

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

Input Schema

NameRequiredDescriptionDefault
idNoSubstance id, e.g. "magnesium", "vit_d".
nameNoSubstance name, e.g. "Vitamin D", as an alternative to id.
detailNoCompact answer by default. Use full for the complete published record.compact
countryNoThe United States is the only market currently available.US

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, closed-world behavior, and the description goes well beyond them by describing the response contents: forms, the applicable country limit first, then other countries' limits with scope, sources and recorded dates. It also discloses a non-obvious semantic behavior (Omega-3 and fish oil resolve to separate EPA and DHA records) and an important scope boundary that the data is reference-only.

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 core action, then return shape, then the detail-level switch, then the scope caveat — a sensible order with no filler. The middle sentences are dense and pack multiple claims into single lines, which slightly reduces scanability but no sentence is redundant.

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?

With no output schema, the description carries the return-shape burden and does so thoroughly (forms, country limit ordering, other limits with sources and dates). Combined with full schema coverage and annotations, an agent has nearly everything needed; only the no-required-params edge case (neither id nor name supplied) is unaddressed.

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

Parameters4/5

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

Schema coverage is 100%, so a 3 is the baseline, but the description adds real meaning: "name" also accepts synonyms and form names, and "detail: full" is tied to concrete extra content (form details, references, product search link). It does not clarify precedence when both id and name are supplied, which is the one remaining semantic gap.

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?

Names a specific verb and resource ("Finds a substance") and enumerates the lookup keys (name, form, synonym, ID), which cleanly separates it from product-oriented siblings like get_product and search_products. It also states the entity is a substance record with forms and country limits, so an agent knows exactly what it retrieves.

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 clear usage context: default compact answers, switch to detail "full" for form details, references and the published-product search link, and explicitly excludes medication interactions, diagnosis and treatment decisions. The gap is that it never names the alternative tool (e.g. check_stack) for the excluded interaction use case, leaving the agent to infer where to go instead.

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