Supplement Advisor MCP Server

check_interactions

Determine which nutrients your medication depletes and get recommended supplements with severity and mechanisms.

Instructions

Check if medications deplete nutrients, creating supplement needs. Returns depleted nutrients, mechanisms, severity, and recommended supplements.

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": {
      "medication": "<medication>"
    },
    "name": "check_interactions"
  }
}

Input Schema

Name	Required	Description	Default
`medication`	Yes	Medication name or class (e.g., 'statin', 'metformin', 'PPI', 'birth-control', 'omeprazole')

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?

No annotations are provided, so the description carries the full burden. It discloses the behavioral outcome and return content in detail, including the types of information returned. It lacks caveats about limitations or data sources, but for a read-only informational tool, this is adequate.

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 concise sentences, front-loaded with the primary purpose and followed by the output specifics. Every word earns its place; no fluff or repetition.

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?

For a single-parameter tool with no output schema, the description covers the purpose and return fields well. It could potentially detail the output structure or mention that multiple results may be returned, but this is not necessary for basic use.

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 schema has 100% coverage, including a description and examples for the 'medication' parameter. The tool description does not add additional parameter semantics beyond what the schema already provides, so the baseline score of 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 checks medication-induced nutrient depletion and explicitly lists the output fields (depleted nutrients, mechanisms, severity, recommended supplements). This specific verb and resource scope distinguishes it from sibling tools like recommend_supplement and get_dosage.

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 clearly implies when to use the tool: when you have a medication and need to know if it depletes nutrients. It gives context but does not explicitly name alternatives or exclusions, so it falls short of a 5.

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

Deploy Server