Aviado Health BioIntelligence

get_supplements_for_condition

Find which supplements help with a health condition or goal (e.g., 'sleep', 'anxiety', 'joint pain'). Returns evidence-graded supplement recommendations with dosages.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max supplements to return, ranked by evidence (default: 25, max: 50)
`condition`	Yes	Health condition, symptom, or goal (e.g., 'insomnia', 'anxiety', 'brain fog', 'joint pain')
`min_grade`	No	Minimum evidence grade to include (default: D = all)	D

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 20, 2026
- addedInput schema / properties / condition / maxLength
```
Added value: +512
```
- addedInput schema / properties / condition / minLength
```
Added value: +1
```
Changed3 schema fields changedJul 1, 2026
- addedInput schema / properties / limit / maximum
```
Added value: +50
```
- addedInput schema / properties / limit / minimum
```
Added value: +1
```
- changedInput schema / properties / limit / type
```
Previous value: -"number"New value: +"integer"
```

Changed1 schema field changedJun 30, 2026

addedInput schema / properties / limit

Added value: +{
+  "default": 25,
+  "description": "Max supplements to return, ranked by evidence (default: 25, max: 50)",
+  "type": "number"
+}

AddedJun 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that results are evidence-graded and include dosages, which are key behavioral traits. However, it does not mention ordering details, potential lack of results, or any limitations beyond what is in the parameter schemas.

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?

The description is two sentences with no filler. It front-loads the tool's purpose and provides a concise output summary, earning every word.

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?

The tool is a simple retrieval query with fully self-describing parameters and a clear return type (evidence-graded recommendations with dosages). No output schema exists, but the description covers the key output semantics. It could be slightly enhanced by explaining the evidence grading scale or explicitly distinguishing from the biomarker sibling, but it is generally complete.

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

Parameters3/5

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

The input schema provides 100% description coverage for all parameters, including defaults and allowed values. The tool description adds minimal parameter meaning beyond examples that already appear in the condition parameter description. Baseline 3 is appropriate.

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?

The description clearly states the tool finds supplements for a health condition or goal, with specific examples like 'sleep' and 'joint pain'. This distinguishes it from siblings such as get_supplements_for_biomarker, which target biomarkers instead.

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 description establishes a clear context for use (when you have a health condition or goal) and mentions the evidence-graded output, but it does not explicitly name alternative tools or state when not to use it. It implies usage rather than providing exclusions.

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

All Aviado Health BioIntelligence tools Inspect

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

Need Help?