pgx_lookup
Which drugs an HLA typing carries a published pharmacogenomic association for. Looks each allele up in hla-pgx-open (CPIC guidelines + PharmGKB clinical annotations, CC BY-SA, snapshot date in every answer) after normalizing the name first, so any era or shorthand works (A3101, B5701, HLA-B*15:02:01G) and every conversion leaves a flag. Returns per allele the current name, the two-field form, the flags and the associations (source, drug, evidence level, CPIC testing recommendation, implication, recommendation, guideline or annotation URL, PMIDs), plus summary.actionable: the CPIC level-A, allele-positive rows. Guideline lookup over published CPIC and PharmGKB associations, keyed by two-field HLA allele. Decision support only; not a medical device. After an allogeneic transplant the recipient's blood carries the donor's genome, and which genome should drive an HLA-mediated drug alert is an open question (NCT06856226); this lookup reports both and decides nothing. Allele strings only, no patient identifiers.
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": "pgx_lookup"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| typing | No | locus -> up to 4 reported allele names. Allele strings only: never patient names, medical record numbers, dates of birth, or accession or case identifiers. | |
| alleles | No | A flat list of reported allele names instead of a typing. Send exactly one of typing or alleles. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| scope | Yes | ||
| alleles | Yes | ||
| license | No | ||
| release | Yes | ||
| summary | Yes | ||
| attribution | No | ||
| pgx_snapshot | Yes | The hla-pgx-open snapshot the answer came from (UTC date and git commit). |