Skip to main content
Glama

Get Test Panels

get-test-panels

Get available test panels and compare panel base prices with their included tests bought separately. One $18 lab & physician order fee applies once per order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get-test-panels"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does supply genuinely useful business behavior — a single $18 lab & physician order fee per order, which affects how prices should be interpreted — but it never states that the operation is read-only or describes the returned structure (panels, included tests, price fields).

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?

Two tight sentences with the primary purpose front-loaded; the fee statement is secondary but earns its place as business context. Nothing is redundant.

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

Completeness3/5

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

For a simple read tool with a single optional parameter and no output schema, the description covers purpose and pricing rules but leaves the category filter and the shape of the returned comparison undocumented — gaps an agent must resolve by trial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one parameter, category, with 0% schema description coverage, and the description never mentions it. The agent must guess that 'category' filters panels and has no guidance on accepted values or matching behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (test panels) and two concrete operations: retrieving available panels and comparing a panel's base price against its included tests bought separately. That price-comparison framing helps distinguish it from the sibling get-test-details, though it never names an alternative explicitly.

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 comparison of panel vs. individual pricing implies the use case (deciding whether a panel is worth it), but there is no explicit when-to-use, no prerequisites, and no direction to compare-prices or search-lab-tests when the agent instead wants individual tests.

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