Skip to main content
Glama

Search Lab Tests

search-lab-tests

Search the JustLabs catalog of tests AND panels by test name, condition (e.g. menopause, gout, anemia), category, or biomarker. Use only product terms; do not include names, contact details, symptoms, or personal lab results. Prices are per test; one $18 lab & physician order fee is added once per order. Use get-pricing for the exact total.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search-lab-tests"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose notable business behavior — per-test prices plus a single $18 lab and physician order fee per order — and a hard constraint on what must not be sent as query text. However, it says nothing about result count, ranking/matching behavior, or whether partial/typo terms are tolerated, which matters for a free-text search with a 100-char cap.

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?

Three sentences, front-loaded with purpose, then the query-hygiene rule, then pricing and the redirect to get-pricing. The pricing sentence is slightly tangential to search but earns its place by pre-empting a common follow-up question and pointing at the right sibling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter search tool with no annotations and no output schema, the description covers what to search by, what not to include, and where to go for totals. The remaining gap is return-value behavior (number of matches, ordering), which the absence of an output schema leaves undocumented.

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?

Schema coverage is 0%, so the description must compensate, and it largely does: it tells the agent the single 'query' parameter accepts product terms across names, conditions, categories, and biomarkers, and explicitly lists prohibited content types. It doesn't mention the 100-character maximum declared in the schema, leaving one concrete limit for the schema alone.

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 ('Search the JustLabs catalog of tests AND panels') and enumerates the four facets the query matches on: test name, condition, category, biomarker. It also explicitly distinguishes the pricing angle from get-pricing, so an agent knows this tool finds products rather than totals.

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?

It gives concrete query-construction rules ('Use only product terms; do not include names, contact details, symptoms, or personal lab results') and names the alternative to use for pricing totals ('Use get-pricing for the exact total'). What's missing is any routing guidance against catalog-adjacent siblings such as recommend-tests or get-test-details, so the when-to-use boundary is clear only in one direction.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources