Picardo

Prepare an order link

prepare_order_link

Read-onlyIdempotent

Create a link to review a lab order on picardo.health for the chosen panels and tests. Nothing is ordered or saved here: the user reviews the order, enters their details and pays on the site. Returns the link, what it contains and anything that could not be included. Orders are for adults 18 and over and are not available to people who live in New York, New Jersey, Rhode Island, Pennsylvania, Maryland, Massachusetts, Hawaii, Maine. picardo.health checks the date of birth and address at checkout and refuses an order from anyone else.

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": "prepare_order_link"
  }
}

Input Schema

Name	Required	Description	Default
`panel_ids`	No	Panel IDs from list_lab_panels.
`test_codes`	No	Six-digit Labcorp codes from search_lab_tests.

Output Schema

Name	Required	Description
`url`	Yes
`tests`	Yes
`panels`	Yes
`nextSteps`	Yes
`notIncluded`	Yes	Requested IDs or codes that could not be included.
`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.
`atHomeDrawUsd`	Yes	At-home blood draw fee for the tests everyone gets: one fee per requisition of up to 40 tests. A Labcorp location is free.
`atHomeDrawUsdForMen`	Yes	Set only when a man’s PSA takes the order into another requisition; otherwise null.
`atHomeDrawUsdForWomen`	Yes	Set only when a woman’s pregnancy test takes the order into another requisition; otherwise null.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), it explains what the link is for, that the user completes details and payment externally, that the response includes the link plus what could not be included, and it discloses hard eligibility limits (18+, eight excluded states, verified at checkout). This is behavior an agent cannot infer from the structured fields and prevents wasted or invalid calls.

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?

Front-loaded with the core action, followed by the 'nothing is ordered' caveat, return contents, and eligibility rules. Every sentence is substantive, though the long state enumeration and the closing checkout-restatement are slightly repetitive.

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?

For a two-parameter link-generation tool with an output schema, the description covers the action, side effects, return contents, and eligibility gating, so an agent has everything needed to call it correctly and to warn the user about age/state limits.

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 coverage is 100% and the schema already documents both parameters, including their source tools and limits. The description adds only that the chosen panels and tests are packed into the link and that exclusions are reported back, so the baseline of 3 applies.

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 ('Create a link to review a lab order') plus the destination ('on picardo.health'), and scopes it to 'the chosen panels and tests', which cleanly separates it from the catalog-browsing siblings (list_lab_panels, search_lab_tests, get_lab_panel).

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?

The description makes the usage context clear: it is the hand-off step after selecting panels/tests, and nothing is ordered or saved, so the agent knows this is a pre-checkout link, not a purchase. It does not explicitly name the sibling tools or state exclusions, so it falls short of a 5.

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?