Wellness Project

list_supplements

Read-onlyIdempotent

List the user's medication/supplement stack and schedules. For questions comparing supplements with sleep, HRV or other metrics, or asking which days items were taken or missed, set include_adherence=true to read recorded daily check-ins.

INFER — do not ask:

filter: default to 'active'; use 'all' for prior periods or ended supplements; 'historical' for ended items only.
category: omit for both categories.

Daily check-ins: maximum 31 days per call; request consecutive windows for longer history. A missing entry means unlogged, NOT missed. Each item includes its id, name, dose, schedule and start/end dates.

Input Schema

Name	Required	Description
`filter`	No	Which items to return. Default: 'active'.
`category`	No	Filter by category; omit for both.
`end_date`	No	With include_adherence: inclusive YYYY-MM-DD end, default today.
`start_date`	No	With include_adherence: inclusive YYYY-MM-DD start, default 29 days before end_date.
`include_adherence`	No	Include taken/missed daily check-ins; default false.

Output Schema

Name	Required	Description	Default
`result`	Yes	Human-readable result text returned by the tool.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 23, 2026

changedInput schema / properties / category / description

Previous value: -"Filter by category. Omit for both."New value: +"Filter by category; omit for both."

addedInput schema / properties / end_date

Added value: +{
+  "description": "With include_adherence: inclusive YYYY-MM-DD end, default today.",
+  "type": "string"
+}

addedInput schema / properties / include_adherence

Added value: +{
+  "description": "Include taken/missed daily check-ins; default false.",
+  "type": "boolean"
+}

addedInput schema / properties / start_date

Added value: +{
+  "description": "With include_adherence: inclusive YYYY-MM-DD start, default 29 days before end_date.",
+  "type": "string"
+}

First observedAug 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses important behavior: maximum 31 days per call, consecutive windows for longer history, and the critical semantic that a missing entry means unlogged rather than missed. It also summarizes what each returned item includes.

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 front-loaded, structured with a clear INFER bullet list, and every sentence adds operational value. There is no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with five optional parameters and an output schema, the description covers the key calling decisions, adherence window limits, default behavior, and return-item semantics. An agent has enough information to invoke it correctly.

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 would be 3, but the description adds useful meaning beyond the schema: default filter behavior, omitting category for both, and the 31-day adherence window with consecutive requests for longer ranges.

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 gives a specific verb and resource: 'List the user's medication/supplement stack and schedules.' It also distinguishes the read-oriented adherence mode from the sibling logging tool 'log_supplement_taken' by explaining that include_adherence reads recorded daily check-ins.

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?

It provides clear guidance for when to set include_adherence=true, including metric-comparison and taken/missed questions, and gives default filter/category behavior. It lacks explicit when-not-to-use guidance or named alternative tools, but the usage context is otherwise strong.

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

All Wellness Project 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.