Skip to main content
Glama

TestWell Lab Tests

by com.test-well

Get a guide, condition or answer page as Markdown

get_guide
Read-onlyIdempotent

Return one of TestWell's educational pages as Markdown: guides (/guides/), condition workups (/conditions/), test decision guides (/answers/), biomarker pages (/biomarkers/), state pages (/lab-locations/) or comparisons (/compare/). Call with no path to list the available guides and conditions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoSpanish version when one exists (default en)
pathNoSite path, e.g. '/guides/annual-blood-work' or 'conditions/anemia'

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds meaningful context: the output format is Markdown, the accepted path categories are given, and the empty-path listing behavior is disclosed. This goes beyond the annotations without contradiction.

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 one tightly written sentence plus one short behavioral instruction. The primary purpose is front-loaded and every clause carries useful information without redundancy.

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, idempotent, non-destructive tool with two optional parameters and no output schema, this description is complete: it covers all supported page types, provides URL templates, notes language availability, and describes the default no-path behavior.

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 input schema provides 100% description coverage for both parameters, so the baseline is 3. The description adds extra semantics by stating that omitting path yields the list of guides/conditions and by listing the valid path prefixes beyond the schema's two examples.

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 the action ('Return') and resource ('TestWell's educational pages as Markdown') and enumerates six specific page types with URL patterns. This clearly distinguishes it from siblings like get_test and search_tests.

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 makes the tool's purpose clear and even specifies the no-path invocation to list available guides. However, it does not explicitly mention when to prefer a sibling tool or provide when-not guidance, which prevents a 5.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Each tool has a distinct primary purpose, but compare_prices and compare_provider have overlapping comparison themes that could lead to misselection if an agent is not careful. The descriptions provide enough context to differentiate them, but the boundary between searching for a test and getting its full detail could also cause minor confusion.

Naming Consistency5/5

All tool names follow a clear verb_noun pattern with consistent snake_case formatting (e.g., calculate_free_testosterone, compare_prices, get_test, list_panels). The naming style is uniform and predictable across the entire set.

Tool Count5/5

13 tools is a well-scoped count for a lab test service covering search, details, pricing, reference ranges, interpretation, comparisons, and educational guides. Each tool earns its place without feeling redundant or bloated.

Completeness5/5

The tool set covers the full user journey: searching and viewing tests, panels, pricing and ordering quotes, reference ranges, interpretation, unit conversion, and finding draw sites. There are no obvious dead ends or significant missing operations for the stated purpose of a consumer-facing lab test information and ordering service.

Resources