Skip to main content
Glama

Supplement Check

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

A supplement's label, dose check and halal status

get_supplement
Read-onlyIdempotent

A supplement's label: amounts per serving, upper limit check, halal status and a buy link. For requests like "what's in Nature Made vitamin D3?", "is Centrum halal?", "how much melatonin is in OLLY Sleep?" or "is this supplement halal?" with a barcode. Give q (brand and product name) or barcode. Returns per-serving amounts, dose_check (each vitamin and mineral compared with the adult upper limit at the most the label suggests per day, with per_day_base amounts), other_checks (melatonin, caffeine, creatine, ashwagandha and similar, including when a blend hides the amount), halal (likely_halal, doubtful, not_halal or depends_on_school, with the ingredients that need a confirmed source), alternatives (other sizes or versions), an Amazon link, and halal_options (links to halal-certified or gelatine-free versions) when the halal answer is not likely_halal. For a general name like "creatine monohydrate" it reads one common label and says so. With country=GB, dose_check uses the NHS guidance where it sets one (upper_limit says NHS guidance). Salt forms such as magnesium glycinate are counted as the mineral they hold (estimated: true), and omega-3 is read from EPA and DHA, total omega-3, or estimated from the fish oil weight.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoBrand and product name, for example Nature Made vitamin D3 2000 IU.
idNoA label id from the NIH database, for example from alternatives.
barcodeNoUPC or EAN barcode digits (8 to 14).
countryNoUS, GB, IE, CA, AU. GB uses NHS guidance for the dose checks; also picks the buy link site. Default from the request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/open-world, and the description adds substantial non-structured behavior: what each result block contains, that ambiguous generic names read one common label 'and says so', that salt forms are counted as their mineral with estimated: true, and that country=GB switches dose_check to NHS guidance. This is rich disclosure beyond the annotations.

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 essence ('A supplement's label: amounts per serving, upper limit check, halal status and a buy link'), then example queries, then the return shape and edge cases. Dense but every sentence adds operational detail; it runs long for a 4-param tool.

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?

No output schema exists, yet the description enumerates the return structure field by field (dose_check, other_checks, halal, alternatives, halal_options) and covers the two major data quirks (salt forms, omega-3 estimation). Nothing an agent needs to call or interpret results is missing.

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 the baseline is 3; the description goes further by explaining what country=GB actually changes (NHS thresholds and buy-link site) and how q behaves for generic vs brand names, plus routing to id from alternatives.

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 resource (a supplement's label) and enumerates what it returns: per-serving amounts, upper-limit check, halal status, buy link. This is far more than a tautology, though it never explicitly contrasts itself with the sibling tools check_dose, check_stack, or get_nutrient, leaving the boundary to be inferred.

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 concrete trigger phrasings ('what's in Nature Made vitamin D3?', 'is Centrum halal?') and states the two lookup routes, q or barcode. No explicit when-not-to-use guidance versus check_dose or check_stack, which is the only gap.

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

All Supplement Check toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources