Skip to main content
Glama

lookup_supplement_grade

Read-only

Look up a supplement by brand and product name in Sally's pre-graded corpus from the NIH Dietary Supplement Label Database, and return the stored grade, score and classification. If nothing matches closely, returns the nearest similar products with exact_match false. Cannot grade from a photo.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_kNoHow many corpus matches to return, nearest first.
productYesBrand and product name as printed on the label, e.g. 'Nature Made Vitamin D3 2000 IU'. Include the brand — matching is much weaker without it.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint and non-destructive. Description adds beyond: 'Cannot grade from a photo' and return behavior for non-exact matches. No contradiction.

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?

Three sentences, front-loaded with purpose. No unnecessary words. Every sentence adds value.

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?

No output schema, but description mentions return fields. Covers return behavior and key limitation. Adequately complete for a lookup tool with rich annotations.

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%. Description adds meaningful constraints: product must be 'as printed on the label', brand inclusion advised, top_k returns nearest first. Adds value over schema.

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?

Clearly specifies action 'look up', resource 'pre-graded corpus from NIH Dietary Supplement Label Database', and return values 'stored grade, score and classification'. Distinguishes from sibling 'supplement_grading'.

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?

Provides context: 'Cannot grade from a photo' and describes fallback behavior. Implicitly guides to use supplement_grading for new grades, but lacks explicit when/alternatives.

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.

TDQS

C2.3/5.0
Disambiguation2/5

Several tool names have overlapping or unclear purposes (e.g., 'health_insights' vs 'metabolic_overview', 'food_journal' vs 'lookup_food', 'supplement_grading' vs 'lookup_supplement_grade'), and most descriptions are generic ('Sally skill') without clarifying distinctions.

Naming Consistency2/5

Tool names mix verb_noun patterns (analyze_lab_result, lookup_food, lookup_supplement_grade, search_health_knowledge) with noun_phrases (chat_with_sally, food_journal, health_insights, health_sync, metabolic_overview, supplement_grading), lacking a consistent convention.

Tool Count5/5

The tool count of 10 is well within the typical 3-15 range and appears appropriate for a health assistant server covering nutrition, supplements, lab results, and general health queries.

Completeness3/5

The tool set covers nutrition, supplements, lab analysis, and health knowledge, but lacks obvious features like activity tracking, medication management, or appointment scheduling, leaving some gaps in a holistic health assistant.

Resources