Skip to main content
Glama

Check a set of supplements

check_stack
Read-onlyIdempotent

Adds known amounts from up to 12 entries, which can be published product names or IDs or ingredient amounts supplied by the person. Returns matched products, known daily amounts and applicable published adult reference comparisons. Daily totals need an amount, unit and stated daily use. For entries supplied as names or ingredient amounts, the answer can show separate comparisons by adult age. ID-only requests use the lower recorded adult reference when age is unknown. Reference data only: it does not cover medication interactions, diagnosis or treatment decisions.

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": {
      "items": "<items>"
    },
    "name": "check_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYesPublished products or ingredient amounts.
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

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, and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: age-split comparisons for name/ingredient entries, the lower-reference fallback for ID-only requests, the requirement of amount+unit+daily use for totals, and an explicit scope limit excluding interactions, diagnosis, and treatment. It does not say what happens to unmatched or ambiguous product names, which keeps it from a 5.

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?

The opening sentence front-loads what the tool does and what it returns, and subsequent sentences each carry distinct rules (entry types, age-split behavior, ID fallback, scope limits). It is dense but nearly every clause is information-bearing. Minor cost: the age-comparison and ID-fallback rules could be merged to reduce sentence count.

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?

There is no output schema, and the description compensates by naming the returned elements (matched products, known daily amounts, published adult reference comparisons). Given three parameters with full schema coverage and closed-world annotations, the definition covers what an agent needs to call it correctly. The only gap is unspecified behavior for entries that fail to match a product.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it clarifies that entries are heterogeneous (name, ID, or ingredient amount), reinforces the 12-entry cap, and explains the relationship between amount, unit, and servings_per_day for totals. The detail and country parameters are not discussed in the description, a minor omission since their schema descriptions already cover them.

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?

The description states a specific operation: it aggregates up to 12 entries (product names, IDs, or raw ingredient amounts) and returns matched products, daily totals, and adult reference comparisons. That is far more specific than the title 'Check a set of supplements' and lets an agent distinguish it from single-lookup siblings like get_product or get_ingredient. It stops short of explicitly naming a sibling, so a 4 rather than a 5.

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 context is implied by the input rules — daily totals require an amount, unit, and stated daily use, and ID-only requests fall back to the lower recorded adult reference — which tells the agent how to shape a call. However, there is no explicit statement of when to choose this over compare_products or search_products, and no statement of when not to use it beyond the reference-data disclaimer. Adequate but leaves routing to inference.

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