Skip to main content
Glama

Get Pricing

get-pricing

Get the exact all-in price for one or more JustLabs test or panel IDs: each item's price, the single $18 per-order lab & physician fee (charged once per order), and the total — the same amount checkout charges. Pass an optional 2-letter US state to check whether the order can be placed there.

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": {
      "testIds": "<testIds>"
    },
    "name": "get-pricing"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateNo
testIdsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the fee model ($18 charged once per order, not per item), guarantees parity with checkout, and explains that the state argument gates orderability. It does not state rate limits, caching, or error behavior for invalid or unavailable IDs, which keeps it short of a 5.

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, front-loaded with the core action and output shape, then the optional parameter. Every clause adds information an agent needs; nothing is redundant with the title.

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?

There is no output schema, so the description's enumeration of return values (item price, single fee, total) is exactly what is needed. Combined with the orderability caveat for state, an agent has enough to call it correctly and interpret the result.

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 description coverage is 0%, so the description must compensate, and it does for both parameters: testIds is described as one or more JustLabs test or panel IDs, and state as an optional 2-letter US state used to check orderability. It omits the cardinality limit (max 50) and the ID format/length bound, which are only in the schema.

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?

States a specific verb and resource ('Get the exact all-in price for one or more JustLabs test or panel IDs') and enumerates exactly what comes back: per-item price, a single $18 per-order fee, and the total. That output decomposition distinguishes it from a comparison tool like compare-prices without needing to name it.

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?

Usage is implied by the verb and by the note that the returned amount is 'the same amount checkout charges', which tells the agent this is the pre-checkout quote path. There is no explicit when-to-use versus when-not guidance, and no named alternative for price comparison scenarios.

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