TestWell Lab Tests

List panels

list_panels

Read-onlyIdempotent

List TestWell's bundled panels (multi-test packages priced below the sum of their tests), optionally filtered by category or maximum price. Sorted by price.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 25)
`category`	No	Catalog category, e.g. 'Hormones', 'General Health'
`maxPrice`	No	Only panels at or under this sticker price (USD)

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No
`labFee`	No	USD
`panels`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "count": {
+      "type": "number"
+    },
+    "labFee": {
+      "description": "USD",
+      "type": "number"
+    },
+    "panels": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "biomarkers": {
+            "description": "Number of biomarkers reported",
+            "type": "number"
+          },
+          "category": {
+            "type": "string"
+          },
+          "labs": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "name": {
+            "type": "string"
+          },
+          "orderUrl": {
+            "description": "Absolute https URL on test-well.com",
+            "type": "string"
+          },
+          "price": {
+            "description": "USD",
+            "type": "number"
+          },
+          "prices": {
+            "additionalProperties": {},
+            "description": "Sticker price per lab; null where the lab does not run the item",
+            "properties": {
+              "bioreference": {
+                "anyOf": [
+                  {
+                    "description": "USD",
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "labcorp": {
+                "anyOf": [
+                  {
+                    "description": "USD",
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              },
+              "quest": {
+                "anyOf": [
+                  {
+                    "description": "USD",
+                    "type": "number"
+                  },
+                  {
+                    "type": "null"
+                  }
+                ]
+              }
+            },
+            "type": "object"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "tests": {
+            "description": "Number of tests in the panel",
+            "type": "number"
+          },
+          "url": {
+            "description": "Absolute https URL on test-well.com",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context beyond that: panels are bundled and priced below the sum of their tests, results are sorted by price, and filters are optional. No contradiction with annotations.

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?

One well-structured sentence that front-loads the core purpose, defines the resource, lists the available filters, and states the sort order. Every part earns its place and there is no redundant wording.

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?

This is a simple list operation with three optional parameters, full schema documentation, and an output schema. The description covers purpose, filtering options, sorting, and pricing semantics. Nothing essential is missing for an agent to invoke it correctly.

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?

Schema description coverage is 100%, so the schema already documents all three parameters clearly. The description adds the 'sorted by price' behavior and pricing semantics but doesn't add parameter-specific meaning beyond what the schema provides. 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 uses a specific verb ('List') and identifies a distinct resource: TestWell's bundled panels. It clarifies what a panel is (multi-test packages priced below the sum of their tests), which differentiates it from sibling tools like search_tests or get_test.

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: use this when the user wants panels, optionally filtered by category or price. It does not explicitly name alternative tools or state when not to use it, but the scope is specific enough that an agent can infer the right situation.

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

All TestWell Lab Tests 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?