Skip to main content
Glama

Compare Prices

compare-prices
Read-onlyIdempotent

Compare the all-in price of one JustLabs test or panel (catalogue id such as tsh, or a test name) with published prices from other direct-to-consumer lab services: each one's price, per-order fees and all-in total, whether it covers the same tests, the source link and the date checked. JustLabs all-in = price + one $18 order fee. Product terms only.

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": {
      "item": "<item>"
    },
    "name": "compare-prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior; the description adds external-source attribution (source link, date checked), identifies per-order fees and all-in total, and fixes the JustLabs all-in calculation at price + one $18 order fee. It also constrains results to product terms only, which is meaningful scope beyond 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.

Conciseness4/5

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

It is front-loaded with the comparison action and scope, and the two follow-up sentences add the fee formula and product-terms limitation without filler. The long first sentence is dense but still earns its place.

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 open-world comparison with no output schema, the description lists the returned comparison fields, source link, date checked, and the JustLabs all-in formula. It still leaves missing-data and response-shape details unspecified, but is otherwise complete.

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 define item; it does by saying it accepts one JustLabs test or panel as a catalogue id such as tsh or a test name, which tells the agent valid formats and an example. It does not cover edge cases like ambiguous names or case sensitivity, so it is not a 5.

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 price for one JustLabs test or panel against published prices from other direct-to-consumer lab services—and details the comparison fields. It is clearly distinguishable from a generic pricing lookup or provider comparison even without naming a sibling.

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 gives clear context—comparison against published DTC lab prices for one JustLabs item—and limits scope to product terms, but it never explicitly says when to choose this over siblings such as get-pricing or compare-provider, nor when not to use it. Usage is therefore implied rather than instructed.

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