Supplement Advisor MCP Server

recommend_supplement

Find the right supplement for your condition with evidence-based recommendations, including clinical evidence, dosing, cost-per-dose, and purchase links.

Instructions

Get evidence-based supplement recommendations for a specific condition. Returns ranked products with clinical evidence, dosing, cost-per-dose, and purchase links.

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": {
      "supplement": "<supplement>"
    },
    "name": "recommend_supplement"
  }
}

Input Schema

Name	Required	Description	Default
`condition`	No	The health condition or goal (e.g., 'sleep', 'anxiety', 'deficiency', 'muscle-building'). Omit for general recommendation.
`supplement`	Yes	The supplement to recommend, e.g. 'magnesium', 'vitamin-d', 'creatine', 'probiotics', 'ashwagandha', 'tongkat-ali', 'zinc', 'l-theanine'. Over 100 supplements are covered; call with an unrecognised name to get the full list.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 7, 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 the main behavior: returning ranked products with clinical evidence, dosing, cost-per-dose, and purchase links. This makes the tool's read-only nature and output format clear, though it could mention edge-case behavior (e.g., invalid inputs).

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?

Two concise sentences front-load the purpose and then detail what is returned. No wordy or redundant explanations.

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 description covers the core function and return format, and the schema is rich. It does not explicitly differentiate from siblings at a usage level, but given the simple nature of the tool and the clear purpose, it is sufficiently 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% coverage with detailed descriptions for both parameters, including examples and the note about unrecognized supplement names. The description adds little beyond the schema, so it meets but does not exceed the baseline.

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's function: 'Get evidence-based supplement recommendations for a specific condition.' It specifies the verb, resource, and context, and it is distinct from sibling tools like compare_forms and get_dosage, which focus on different aspects.

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 provides clear context for when to use the tool ('for a specific condition') and mentions the ability to omit condition for a general recommendation. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous enough for an agent to infer when to use this tool over siblings.

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

Deploy Server