Skip to main content
Glama

Good Turn Studio (all tools)

by io.github.GoodTurnStudio
OverviewDiscussionsAdmin

Supplement Check: Compare an amount of a vitamin or mineral with the adult RDA and upper limit

supplementcheck_check_dose
Read-onlyIdempotent

Supplement Check. Compare an amount of a vitamin or mineral with the adult RDA and upper limit. Use for "is 5000 IU of vitamin D too much?", "is 500 mg of magnesium glycinate safe?", "is 10 mg of melatonin a lot?" or "is 300 mg of caffeine too much?". Handles IU, mcg, mg and g, including IU for vitamins A, D and E and DFE for folate. For vitamins and minerals, status is above, at, within or no_upper_limit; when the name is a compound (magnesium glycinate, ferrous sulfate, zinc gluconate) the compound field also gives how much of the mineral the compound holds, as US and UK labels list the mineral itself; when only one reading is over the limit, the say line gives both and compared_with.depends_on_label is true. Fish oil, cod liver oil and krill oil amounts are the oil weight, so EPA plus DHA is estimated (amount.epa_dha_estimate_mg). With country=GB the limit is the NHS guidance (compared_with.reference is UK (NHS), with us_upper_limit alongside). For other supplements the answer compares with an official ceiling where one exists (caffeine) or the amounts studies have used, with status above, at, within, above_studied_range, within_studied_range, below_studied_range or no_set_amount, plus cautions. Adult values only, with a note

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoThe whole question instead, for example 5000 IU vitamin D.
unitNoIU, mcg, mg, g, mcg DFE, or billion (CFU) for probiotics. Defaults to IU for vitamin D amounts of 200 or more, otherwise the usual unit.
amountNoThe amount taken per day, in the unit given.
countryNoTwo-letter country code. GB compares with NHS guidance and gives UK amounts. Default from the request.
nutrientNoThe vitamin, mineral or supplement, for example vitamin D, magnesium or melatonin.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses real behavioral traits: the status vocabularies for both nutrients and other supplements, the compound-to-mineral conversion behavior, the fish-oil EPA+DHA estimation, the country=GB NHS reference switch, and the adult-only scope note. This is exactly the extra context annotations cannot supply.

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

Conciseness3/5

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

It is front-loaded well, leading with the core purpose and examples before the edge-case caveats. However, the later half is a dense run-on of semicolon-joined clauses covering compounds, fish oil, UK mode and studied ranges, which is harder to parse than a structured breakdown would be.

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?

There is no output schema, so the description carries the return-value burden, and it does: it names the status enums, the compared_with.reference and depends_on_label fields, and amount.epa_dha_estimate_mg. Combined with annotations covering the safety profile, an agent has everything needed to call and interpret this tool.

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% (baseline 3), but the description adds meaning the schema does not: which units apply to which nutrients (IU for A/D/E, DFE for folate), CFU for probiotics, and the compound/unit interactions that affect interpretation. That is genuine added value over the parameter table.

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 ('Compare an amount of a vitamin or mineral with the adult RDA and upper limit') and immediately anchors it with four concrete example questions. An agent can distinguish this from supplementcheck_get_nutrient and supplementcheck_get_supplement without opening a schema.

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?

The example queries ('is 5000 IU of vitamin D too much?', 'is 300 mg of caffeine too much?') make the intended trigger scenario very clear. It does not, however, explicitly route the agent away from the sibling tools get_nutrient/get_supplement or state when not to use it, so it stops short of a full when/when-not statement.

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

All Good Turn Studio (all tools) 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