Picardo

Get a lab panel

get_lab_panel

Read-onlyIdempotent

Get one Picardo panel: every test it includes, marking any for men only or women only, why the tests were chosen, preparation such as fasting, and the subtotal.

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": {
      "panel_id": "<panel_id>"
    },
    "name": "get_lab_panel"
  }
}

Input Schema

Name	Required	Description	Default
`panel_id`	Yes	A panel ID from list_lab_panels.

Output Schema

Name	Required	Description
`id`	Yes
`name`	Yes
`summary`	Yes
`audience`	Yes
`testCount`	Yes	Tests everyone gets; checkout adds any for one sex only.
`preparation`	Yes
`subtotalUsd`	Yes	Price in US dollars of the tests everyone gets, before any blood draw fee. Checkout adds PSA for men and a pregnancy test (hCG) for women. Null when a test is temporarily unavailable.
`whyItMatters`	Yes
`atHomeDrawUsd`	Yes	At-home blood draw fee for this panel; a Labcorp location is free.
`includedTests`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world, and non-destructive behavior, so the safety profile is covered. The description adds useful content about what is returned (gender flags, selection rationale, prep requirements, subtotal), but says nothing about failure behavior for an unknown or expired panel_id, or about any access constraints. With annotations carrying the operational profile, a 3 is appropriate.

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?

One sentence, zero filler, front-loaded with the verb and resource followed by a compact enumeration of the returned fields. Nothing in it is redundant or misplaced.

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?

This is a simple single-parameter read tool with full schema coverage and an output schema, so return-value explanation is not required, yet the description still summarizes the payload helpfully. The only shortfall is the absence of any note on what happens with an invalid panel ID or how this differs from the sibling lookup tools.

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

Parameters3/5

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

Schema description coverage is 100% for the single parameter, and the schema already states panel_id is "A panel ID from list_lab_panels." The description adds no format, length, or validity information beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource ("Get one Picardo panel") and enumerates exactly what the response contains: included tests, gender restrictions, selection rationale, preparation like fasting, and subtotal. The singular "one ... panel" implicitly separates it from list_lab_panels, but the description never names the sibling 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?

Usage is only implied: an agent infers it should call this when it already has a panel ID (which the schema confirms comes from list_lab_panels). There is no explicit when-to-use or when-not-to-use statement, and no guidance on choosing between this and search_lab_tests for test-level lookups.

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

All Picardo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?