TestWell Lab Tests

Get a test or panel

get_test

Read-onlyIdempotent

Full public detail for one TestWell test or panel by slug or id: description, biomarkers, CPT, per-lab prices, labs, fasting/prep, turnaround, included tests (panels), FAQ, related conditions, order URL and a Markdown page URL.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`lang`	No	Spanish prose where a translation exists (default en)
`slug`	Yes	Catalog slug (from search_tests) or id, e.g. 'tsh', 'general-wellness-panel'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`item`	No
`found`	No
`suggestions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 8, 2026

addedOutput schema / properties / item / properties / measuredTurnaround

Added value: +{
+  "description": "Measured medians from real orders (specimen at lab → results), per lab; published only when n ≥ 30. Empty until enough data exists.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "asOf": {
+        "type": "string"
+      },
+      "lab": {
+        "type": "string"
+      },
+      "medianDays": {
+        "type": "number"
+      },
+      "n": {
+        "type": "number"
+      },
+      "p90Days": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "lab",
+      "n",
+      "medianDays",
+      "asOf"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "found": {
+      "type": "boolean"
+    },
+    "item": {
+      "additionalProperties": {},
+      "properties": {
+        "aliases": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "biomarkerCount": {
+          "type": "number"
+        },
+        "biomarkers": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "category": {
+          "type": "string"
+        },
+        "cpt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "description": "CPT code when verified"
+        },
+        "currency": {
+          "type": "string"
+        },
+        "description": {
+          "type": "string"
+        },
+        "fastingRequired": {
+          "type": "boolean"
+        },
+        "id": {
+          "type": "string"
+        },
+        "labFee": {
+          "description": "Flat per-order lab processing fee (charged once per order)",
+          "type": "number"
+        },
+        "labs": {
+          "description": "Labs that run it: Quest, Labcorp, BioReference",
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "markdownUrl": {
+          "description": "Absolute https URL on test-well.com",
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "orderUrl": {
+          "description": "Prefilled cart link",
+          "type": "string"
+        },
+        "orderable": {
+          "type": "boolean"
+        },
+        "popular": {
+          "type": "boolean"
+        },
+        "prepInstructions": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "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"
+        },
+        "resultsIn": {
+          "description": "Turnaround, e.g. '1-3 business days'",
+          "type": "string"
+        },
+        "reviewedAt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "sampleType": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "type": {
+          "enum": [
+            "test",
+            "panel"
+          ],
+          "type": "string"
+        },
+        "url": {
+          "description": "Absolute https URL on test-well.com",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "suggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare the operation as read-only, idempotent, and non-destructive, so the description only needs to add contextual behavior. It does so by emphasizing 'full public detail', which signals no authentication or private data, and by listing the specific response fields. 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?

A single well-structured sentence front-loads the core action and resource, then efficiently lists the full set of returned data. There is no filler or repetition of annotation details.

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?

Given the rich annotations, complete parameter schema, and presence of an output schema, the description provides all essential context: what is returned, how the resource is identified, and the public nature of the data. No critical gaps remain for an agent to call this tool 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%, and the schema already documents both parameters with examples and enum values. The description's 'by slug or id' phrasing slightly reinforces the slug parameter but does not add meaningful new semantics beyond the schema.

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 verb ('Get full public detail'), the resource ('one TestWell test or panel'), and the lookup mechanism ('by slug or id'). It enumerates the returned contents, making it easy to distinguish from sibling tools like search_tests or list_panels.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is the tool to use when a complete detail view of one test or panel is needed, and the slug schema description points to search_tests as the source. However, it does not explicitly state when not to use it or name alternative tools, so usage guidance is left somewhat to inference.

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?