TestWell Lab Tests

Compare all-in prices across providers for a test

compare_prices

Read-onlyIdempotent

For one blood test, the all-in single-test price (sticker + per-order fees) at TestWell and at every tracked direct-to-consumer provider with a verified equivalent — JustLabs, Quest, Labcorp OnDemand, Ulta Lab Tests, Walk-In Lab, HealthLabs and more — each with the date it was verified, plus typical hospital self-pay and Quest Direct reference prices. States the multi-test caveat (fees are paid once per order). Source: the TestWell Blood Test Price Index (CC BY 4.0).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`test`	Yes	Test slug or name, e.g. 'tsh', 'lipid panel', 'vitamin-d'

Output Schema

TableJSON Schema

Name	Required	Description
`hint`	No
`test`	No
`found`	No
`query`	No
`caveats`	No
`dataset`	No	Absolute https URL on test-well.com
`license`	No
`providers`	No	Sorted by all-in price, TestWell included
`reference`	No
`methodology`	No
`cheapestSingleTestAllIn`	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": {
+    "caveats": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "cheapestSingleTestAllIn": {
+      "additionalProperties": {},
+      "properties": {
+        "allIn": {
+          "description": "Sticker + that provider's per-order fees, one test ordered alone",
+          "type": "number"
+        },
+        "note": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "perOrderFees": {
+          "description": "USD",
+          "type": "number"
+        },
+        "pricedAt": {
+          "description": "Date the price was verified (YYYY-MM-DD)",
+          "type": "string"
+        },
+        "provider": {
+          "type": "string"
+        },
+        "providerName": {
+          "type": "string"
+        },
+        "sticker": {
+          "description": "USD",
+          "type": "number"
+        },
+        "url": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "dataset": {
+      "description": "Absolute https URL on test-well.com",
+      "type": "string"
+    },
+    "found": {
+      "type": "boolean"
+    },
+    "hint": {
+      "type": "string"
+    },
+    "license": {
+      "type": "string"
+    },
+    "methodology": {
+      "type": "string"
+    },
+    "providers": {
+      "description": "Sorted by all-in price, TestWell included",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "allIn": {
+            "description": "Sticker + that provider's per-order fees, one test ordered alone",
+            "type": "number"
+          },
+          "note": {
+            "anyOf": [
+              {
+                "type": "string"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "perOrderFees": {
+            "description": "USD",
+            "type": "number"
+          },
+          "pricedAt": {
+            "description": "Date the price was verified (YYYY-MM-DD)",
+            "type": "string"
+          },
+          "provider": {
+            "type": "string"
+          },
+          "providerName": {
+            "type": "string"
+          },
+          "sticker": {
+            "description": "USD",
+            "type": "number"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "query": {
+      "type": "string"
+    },
+    "reference": {
+      "additionalProperties": {},
+      "properties": {
+        "hospitalTypical": {
+          "anyOf": [
+            {
+              "description": "USD",
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "questDirect": {
+          "anyOf": [
+            {
+              "description": "USD",
+              "type": "number"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "test": {
+      "additionalProperties": {},
+      "properties": {
+        "category": {
+          "type": "string"
+        },
+        "cpt": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "name": {
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context: prices include verification dates, reference prices are included, the multi-test caveat is disclosed, and the data source is provided. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and packs in relevant details such as provider list, verification dates, and fee composition. It is somewhat dense and long, but each element contributes to correct tool selection and invocation.

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?

The description fully explains what price components are included, which providers are covered, the verification-date aspect, reference prices, and the multi-test caveat. Combined with a rich output schema and safety annotations, nothing essential for calling the tool correctly is missing.

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 coverage is 100% and the parameter already includes examples and a clear description. The description reinforces that the parameter represents one blood test, but does not add significant meaning beyond what the schema already provides.

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 states a specific verb and resource: compare all-in prices across providers for one blood test. It precisely defines scope (single-test, sticker + per-order fees), enumerates the providers, and mentions verification dates and reference prices, clearly distinguishing it from generic search or quote tools.

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 scopes usage to a single blood test and explicitly calls out the multi-test caveat, so an agent understands when this tool applies. It does not explicitly name alternatives or state when not to use it, but the context is clear enough.

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?