TestWell Lab Tests

All-in order quote

quote_order

Read-onlyIdempotent

Price a set of tests/panels exactly as TestWell's checkout would: per-lab prices for the user's state (New York and New Jersey route to BioReference; Rhode Island is not served), the single $6 lab processing fee, the total, items that can't be ordered and why, and a prefilled cart URL. Use this before quoting any total to a user.

Input Schema

TableJSON Schema

Name	Required	Description
`lab`	No	Preferred lab outside NY/NJ (default quest)
`items`	Yes	Catalog slugs or ids, e.g. ['tsh', 'vitamin-d']
`state`	No	US state code or name where the user will be drawn, e.g. 'FL' or 'Florida'

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	No
`lab`	No
`error`	No	Present when ok=false, e.g. state not served
`lines`	No
`notes`	No
`state`	No
`total`	No	All-in total: subtotal + the single lab processing fee
`labFee`	No	USD
`labName`	No
`currency`	No
`subtotal`	No	USD
`checkoutUrl`	No	Prefilled cart on test-well.com — purchases complete there; null when nothing is orderable
`unavailable`	No	Requested items the routed lab cannot run in this state

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": {
+    "checkoutUrl": {
+      "anyOf": [
+        {
+          "description": "Absolute https URL on test-well.com",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Prefilled cart on test-well.com — purchases complete there; null when nothing is orderable"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "error": {
+      "description": "Present when ok=false, e.g. state not served",
+      "type": "string"
+    },
+    "lab": {
+      "type": "string"
+    },
+    "labFee": {
+      "description": "USD",
+      "type": "number"
+    },
+    "labName": {
+      "type": "string"
+    },
+    "lines": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "lab": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "price": {
+            "description": "USD",
+            "type": "number"
+          },
+          "slug": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "url": {
+            "description": "Absolute https URL on test-well.com",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "notes": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "state": {
+      "type": "string"
+    },
+    "subtotal": {
+      "description": "USD",
+      "type": "number"
+    },
+    "total": {
+      "description": "All-in total: subtotal + the single lab processing fee",
+      "type": "number"
+    },
+    "unavailable": {
+      "description": "Requested items the routed lab cannot run in this state",
+      "items": {},
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important runtime behavior: NY/NJ route to BioReference, Rhode Island is not served, a single $6 processing fee, and the response includes blocked items with reasons and a cart URL. These details are substantive and consistent with the 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?

Two sentences contain dense, essential information with no filler. The main purpose and output contents are front-loaded, followed by a single high-value usage directive.

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 quoting tool with an output schema, the description covers pricing logic, state special cases, fee, blocked items, and the cart URL. Nothing needed to correctly invoke and interpret the tool is missing.

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?

The schema already documents all three parameters, so the baseline is 3, but the description adds meaning by explaining that state influences lab routing (with specific NY/NJ/RI behavior) and that items are tests/panels for pricing. This exceeds what the schema descriptions alone state.

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 opens with a specific verb and resource: 'Price a set of tests/panels exactly as TestWell's checkout would.' It enumerates concrete outputs (per-lab prices, $6 fee, total, unorderable items with reasons, prefilled cart URL), which clearly separates it from siblings like compare_prices.

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 closing directive 'Use this before quoting any total to a user' is an explicit trigger for when to invoke the tool. It does not explicitly name sibling alternatives or give when-not conditions, so it falls just short of full guidance.

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?